Database Info

[HOWTO] Flash a custom ROM/zip and keep Knox cool

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.

4.3 bootloader/No knox/no binary count/wi-fi working (Alternative) for GT-N7100

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.

Rooted stock Lollipop 5.0.1 with Knox 0x0

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.

MT7-TL10 EMUI 3.0 B131 update to Lollipop or Marshmallow

Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced

M.Maany said:
Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
Click to expand...
Click to collapse
I just had this problem a month ago, same build number and barely any help. But, I was able to find helpful posts in the end. So I'm here to help... and yes. First Lollipop then Marshmallow update.
As you probably know, BACKUP what you need before proceeding.
Then you need to:
1- Unroot your phone if you have root.
2- Have EMUI's stock recovery. You can reinstall it in case you've installed a custom recovery on the phone.
3- Factory reset your device (HIGHLY ADVICE to do but not mandatory).
4- Download Lollipop update (to B326) from here: http://ministryofsolutions.com/2016/02/huawei-mate-7-lollipop-511-upgrade-for.html
5- After you finish the download, extract the "UPDATE.APP" file from it (no need to extract anything else from the archive), create a folder called "dload", and put "UPDATE.APP" in that folder.
6- Once you've done that, you should go to updater in your settings, select "local update". This time, the phone should detect the file "UPDATE.APP".
7- Next, attempt to update. The device should restart and attempt to install the update.
From my experience, the update took about 30 minutes to install, since I didn't factory reset before update. So, I don't know if it'll take less time with a clean device.
To update to marshmallow AFTER you've installed lollipop, simply find the OTA update online, download it, and repeat steps 5 to 7.
If anything of what I said was unclear, missing files to download, or you have any questions, feel free to post again here and I'll try to reply back.
Hopefully everything goes well with you, and have a good day.
Credit goes mostly to Mutahhar Bashir for posting the above site of the update.
EDIT:
P.S.: For bootloader re-lock, I personally don't think it's a must, since it worked updating ota with unlocked bootloader for me.

Highly appreciated my friend
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.

M.Maany said:
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
Click to expand...
Click to collapse
Found it on another site. This should be it: http://forum.android.com.pl/topic/2...recovery-sterowniki-mt7-l09-mt7-tl10/?page=27
Sorry I took long, had difficulty finding the file. Install the recovery version that you are CURRENTLY in. The file is called "Recovery mate7 mobopx v2.2". You'll find it on a specific reply on that page.
Keep me up-to-date with your progress for me to see if I can help.

Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant, u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?

M.Maany said:
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
Click to expand...
Click to collapse
Oh I was unclear. Sorry.
What I meant is, that the stock recovery you want to install should be the same as the android version of your phone currently. As in you are currently on Kitkat, then choose to install the kitkat stock recovery from the application.
I hope it's clear right now.

unable to install stock recovery
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
{
"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"
}
cscl.6te.net/Capture.JPG
any idea how to fix it?
by the way, i used kingroot to root my device, don't know if that's related.

Uhm... Just a few suggestions.
M.Maany said:
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
any idea how to fix it?
Click to expand...
Click to collapse
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.

iDoFatalities said:
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
Click to expand...
Click to collapse
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot

M.Maany said:
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
Click to expand...
Click to collapse
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.

ugggg
iDoFatalities said:
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
Click to expand...
Click to collapse
i uninstalled kingroot and this unrooted my device, installed adb drivers from clockworkmod site, installed hisuite from huawei site, already have usb debuggine enabled, but still getting same error
any alternative way to restore stock recovery?
can do the update.app manual update without restoring stock recovery?

uggggg
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?

M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
if I lock the bootloader then unlock it again, would that help? if yes, how do i re-lock it

M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
You MUST have stock recovery for OTA updates. Sorry.
You can try relock then unlock. But i specifically dont know how to. I think there is an app you can find on the tools/utilities tab of this device for utilities for the Mate7, which i think has a relock bootloader option, and many more utilities.
Other than that, I don't know yet how to help you man. For the meantime, surf the internet if you can find anything that can help.
I apologize.
EDIT: Doesn't your phone reboot into bootloader when trying to install? And have you made sure if the recovery has changed?

thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.

M.Maany said:
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
Click to expand...
Click to collapse
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.

YAYYYY !!!!
erayrafet said:
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
Click to expand...
Click to collapse
FINALLY !!!, tried unlocking bootloader again and it worked, although it took forever to get the unlock code.
anyway, now I have stock EMUI recovery, will remove root and do the OTA and let you know how it goes.

ON lollipop
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?

M.Maany said:
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
Click to expand...
Click to collapse
Yes.

AWESOME
Awesome !! now do you have a link for me to download the UPDATE.APP for Marshmallow?
or does it need to be updated in some other way?

S7 flat FRP lock - please help me

this thread is solved !
you basically only need to flash the AP part of an original stock rom which you can download from here:
https://updato.com/firmware-archive-select-model
flash it with odin in downloadmode (you even keep all your apps and settings) ..
{
"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"
}
-------------------------------------------------------------------------------------------------------------------
device: SM-G930F ...
on stock firmware , oreo september 2018 update
installed twrp and magisk
i dont know why it happend
maybe
A) because i finally made a google account ( i didnt want to but thought i just remove it after downloading apps from the appstore )
or B) forgetting to RE-enable oem unlock option, after installing twrp and magisk ...
the frp lock began after i once went into download mode (but didnt flash anything , i wanted to go to twrp but pressed the wrong button so i ended up in download mode)
but it could also be the google lock .
anyways the phone doesnt start anymore so i cannot input my google account credentials .
DO I JUST HAVE TO WAIT FOR 72 HOURS ?
this is the code in odin mode :
I have a full twrp backup of everything on my sdcard , can this help me ?
I also know my google credentials and my phone number is registered.
MY QUESTIONS:
1) which image should i flash ? the newest oreo (8.0) update from december or an earlier version ?
2) do i have to wait for 72 hours ?
3) im in the eu and the phone is 4 days old , should i just claim my warranty or ist it even fixable ? the version before was from september 2018
see here for all versions : which one should i choose ?
https://updato.com/firmware-archive...0F&exact=1&r=VD2&v=Oreo(Android+8.0.0)&rpp=15
thanx in advance , please help me guys
edit: i read that if nothing help i have to flash combination rom for bootloader v3 , is this the correct combination rom ?
http://forum.gsmhosting.com/vbb/f777/g930f-combination-binary-3-download-no-password-2471123/

Ulf3000 said:
device: SM-G930F ...
on stock firmware
installed twrp and magisk
i dont know why it happend
maybe
A) because i finally made a google account ( i didnt want to but thought i just remove it after downloading apps from the appstore )
or B) forgetting to RE-enable oem unlock option, after installing twrp and magisk ...
the frp lock began after i once went into download mode (but didnt flash anything , i wanted to go to twrp but pressed the wrong button so i ended up in download mode)
but it could also be the google lock .
anyways the phone doesnt start anymore so i cannot input my google account credentials .
DO I JUST HAVE TO WAIT FOR 72 HOURS ?
this is the code in odin mode :
I have a full twrp backup of everything on my sdcard , can this help me ?
I also know my google credentials and my phone number is registered.
MY QUESTIONS:
1) which image should i flash ? the newest oreo (8.0) update from december or an earlier version ?
2) do i have to wait for 72 hours ?
3) im in the eu and the phone is 4 days old , should i just claim my warranty or ist it even fixable ? the version before was from september 2018
see here for all versions : which one should i choose ?
https://updato.com/firmware-archive...0F&exact=1&r=VD2&v=Oreo(Android+8.0.0)&rpp=15
thanx in advance , please help me guys
edit: i read that if nothing help i have to flash combination rom for bootloader v3 , is this the correct combination rom ?
http://forum.gsmhosting.com/vbb/f777/g930f-combination-binary-3-download-no-password-2471123/
Click to expand...
Click to collapse
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

PoochyX said:
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
can i flash or convert the twrp backup ? twrp on the phone is not accessable at the moment , i can only boot into download mode
it happend because you have to wipe and after wiping the developer options are reset ... no tutorial specifically mentions to enable oem unlock again after rooting ...
Click to expand...
Click to collapse

Ulf3000 said:
PoochyX said:
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
can i flash or convert the twrp backup ? twrp on the phone is not accessable at the moment , i can only boot into download mode
Click to expand...
Click to collapse
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse

PoochyX said:
Ulf3000 said:
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
ok the latest version from december ? or an older version ? i have downloaded this one :
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
edit: is it enough to flash ap ? thats the bootloader and os image i guess ?
edit2:
BL=Bootloader
AP=Applikationen
CP =Modem
CSC=Country Specific Code
correct ? do i have to flash them all or is bl and ap enough or just bl ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Ulf3000 said:
PoochyX said:
Ulf3000 said:
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
ok the latest version from december ? or an older version ? i have downloaded this one :
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
edit: is it enough to flash ap ? thats the bootloader and os image i guess ?
Click to expand...
Click to collapse
If it's the one you was just using you should be good to go if it's an older one it could not work cuss bootloader locks after certain versions and you can only go up [emoji115]
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Click to expand...
Click to collapse

HOLY **** ! it worked
i ONLY flashed AP btw (i installed twrp and magisk to AP ), i didnt flash the other files.
Then it installed
restartet
upgraded system
went into recovery
and then i had to just reboot .. the apps were prepared and istalled and everything is back to normal, just magisk, twrp and xposed are gone ...
NOW IS THERE A WAY TO COMPLETELY DISABLE FPR checking so this can never happen again ???
------------------------------------------------------------------------------------------------------------
edit: thank you so much for ensuring me to just do it ,. i was hesitant becasue i read a lot of horror stories here !

Ulf3000 said:
HOLY **** ! it worked
i ONLY flashed AP btw (i installed twrp and magisk to AP ), i didnt flash the other files.
Then it installed
restartet
upgraded system
went into recovery
and then i had to just reboot .. the apps were prepared and istalled and everything is back to normal, just magisk, twrp and xposed are gone ...
NOW IS THERE A WAY TO COMPLETELY DISABLE FPR checking so this can never happen again ???
------------------------------------------------------------------------------------------------------------
edit: thank you so much for ensuring me to just do it ,. i was hesitant becasue i read a lot of horror stories here !
Click to expand...
Click to collapse
You welcome.....
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]

mods please put a [SOLVED] in the thread title ,
i think many people fail because BL=Bootloader cannot be flashed when frp bootloop is happening and they try to install all modules at once and then give up or go for unorthodox methods and hardbrick

Ulf3000 said:
mods please put a [SOLVED] in the thread title ,
i think many people fail because BL=Bootloader cannot be flashed when frp bootloop is happening and they try to install all modules at once and then give up or go for unorthodox methods and hardbrick
Click to expand...
Click to collapse
As long as you back up and running [emoji125]
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]