Database Info

Difference between unlocking bootloader and rooting

Does unlocking the bootloader give you root?
And in which instances can you flash a custom recovery or customs ROMs?

Rooting means you can install apps that require root access (like titanium backup or setcpu). Unlocked bootloader means you can load any rom, kernel, etc that you like. Unlocked bootloader is usually acquired after rooting.

I'm not sure I totally understand the first reply, so here is my take on it.
Rooting will let you install apps that require root as already stated, but rooting will let you install custom ROMs and do just about any tweak you want. I finally did unlock my bootloader, but the only benefit I gained was being able to change the flash screen, which is the first screen you see when the phone powers on.
I have read that it's harder to brick your phone with a s=off bootloader too.

It is not harder to brick your phone with an unlocked bootloader, just easier to recover from a soft-brick. An unlocked bootloader will allow you to flash using fastboot. So in the case of a corrupt recovery, or something along those lines, you are able to flash it using your computer. It basically allows you to flash different parts of an image separately.

lowandbehold said:
It is not harder to brick your phone with an unlocked bootloader, just easier to recover from a soft-brick.
Click to expand...
Click to collapse
That's pretty much what I meant, I just didn't say it right. Thanks for clearing it up.

How to find my phones' bootloader is locked or not? Because i already flashed different custom ROMs and using it.
Regards,
Cjey

If you are rooted with a custom recovery, your bootloader is unlocked.

lowandbehold said:
If you are rooted with a custom recovery, your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks buddy,
I want to know that what if i flash ROM for locked bootloaders?

Honestly, I didn't know you can root your phone till today I read a few posts here. So thank you all guys for the input

slight confusion over rooted
i had the .67 generic uk firmware, i downloaded the central europe .73 firmware and used flashtool to flash the ftf file,
all worked fine once i installed the drivers on flash tool,
my confusion is...... alot of people are saying there phone is rooted/bootloader unlocked, am i rite in thinking my phone is rooted and not unlocked,
others have also said they have flashed the .img to the phone which i havent done, is there something ive done wrong ?

[ROOT] Root NVidia Shield Tablet - Lollipop (also locked bootloader)

Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet

Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again

FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.

sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.

Thank you worked great!

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?

Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.

Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul

Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)

Help
Anyone else not able to download supersu.zip the page wont load

Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!

root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.

Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless

cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.

Can i follow this guide to unlock and root 5.0.1?

[Q] Help with installing lollipop on unlocked phone

Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore

ImmoralCore said:
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
Click to expand...
Click to collapse
Your DRM keys are lost forever.

TheTeslaCoil said:
Your DRM keys are lost forever.
Click to expand...
Click to collapse
Ok, so they are lost even if I use the first backup that was made by the person I bought it from ?
DRM=Hardcoded=Once unlocked, always DRM free, even if you use the recovery image ?
And the rest of the questions, what am I supposed to do to get stock lollipop?
In the matter of fact it does not matter if its unlocked or locked, I just want legit lollipop, with the possibility to update regularly. (But if root is possible at the same, it can still be rooted)
Thanks for your reply !

You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.

TheTeslaCoil said:
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
Click to expand...
Click to collapse
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?

ImmoralCore said:
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
Click to expand...
Click to collapse
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.

gregbradley said:
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
Click to expand...
Click to collapse
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?

ImmoralCore said:
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
Click to expand...
Click to collapse
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward

gregbradley said:
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
Click to expand...
Click to collapse
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:

ImmoralCore said:
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
Click to expand...
Click to collapse
Good luck.

Update 6.0 mm full tmo & skinny debloated version

6.0 Marshmallow with insecure modded kernel and TWRP recovery​
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
New debloated version with insecure kernel and init.d support, rooted with Chainfire's Beta 2.71 SuperSU credit to SuperR for the help with the updater perms.
FIXED DOWNLOAD ALL APOLOGIES
Skinny Stylo Alpha version
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started

Saved

Requirements- Unlocked bootloader
Click to expand...
Click to collapse
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.

runningnak3d said:
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
Click to expand...
Click to collapse
@runningnak3d
I would prefer to be bootloader unlocked through fastboot oem unlock before doing any mods in 6.0. Every single time I did not I got secure boot error. If you make any system change on 6.0 with locked boot it will not boot.

Thank you for taking the time to do this.
:good::good:

So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.

Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
The main reason I made this was because I can never boot recovery or fastboot manually ( ex. w/hardware buttons) when you have the insecure kernel adb works when at the splash screen so it's easier to recover if you have any problems.
Sent from my LG-H631 using XDA-Developers mobile app

Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.

wrenchman76 said:
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
Click to expand...
Click to collapse
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.

runningnak3d said:
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
Click to expand...
Click to collapse
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?

wrenchman76 said:
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
Click to expand...
Click to collapse
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.

Waiting on the debloated version.
Sent from my LGMS631 using Tapatalk

runningnak3d said:
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Click to expand...
Click to collapse
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.

Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You didn't need to ship it back to LG. Firmware download mode is always available (hold vol up while plugging in USB cable -- just vol up, not vol up + power). Continue holding vol up until FW DL mode displays). Then just use the LG flash tool to flash a KDZ. It is a PITA when you have to go back that far, but you can't brick these phones, not with software at least -- they would need to be physically altered
-- Brian

Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You sent your device in for a soft brick? You should set up the flash tool for our phone with a 10j.kdz before doing anything. Hope you get it back soon.

Debloated version
Fixing some force close problems on a debloated version now, should be up later today or tonight.

@runningnak3d
Flashing the KDZ seems easy enough. But how could I fix it without unrestricted access to a computer? And my stock charger is broken without a USB cable. I had no choice but to send it in for repairs. Guess I'll be stuck on Lollipop for a while longer, at least.

Edubyah said:
6.0 Marshmallow with insecure modded kernel and TWRP recovery​
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Click to expand...
Click to collapse
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)

JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
Can the bootloader be unlocked on the CDMA versions (ex. Boost, Sprint, Verizon)? If you can I will make a variant for it. But if you can't NO.
I just found out that the unlocked bootloader in 6.0 survives even the .kdz flashtool. So once you unlock your boot in 6.0 with fastboot oem unlock you never have to do it again even survived kdz downgrade to lollipop and update to 6.0 stayed unlocked.

JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
works great on metro ms631 just need wifi to stop turning its self off can you guys fix it! h631/ms631 mm kernel works find no errors help needed fixing wifi connection thanks

Trying to Restore Phone to Stock (and a few other questions)

Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0

If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.

shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?

Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.

shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^