Database Users

[FAQ][ROOT]Answers to Questions about Root

All Your Root Questions Answered:​
This thread is a work in progress. Ask your root questions, and I'll answer them in the OP. This way we can clean up the other thread.
Thank you @DmdStar, @somberfox, @CrashXXL, and everyone else I missed (which I will add to the OP)
Q: I followed all the directions and after I finished the root procedure, my device is stuck at the M logo? HALP.
A: You didn't follow all the directions, and now you're going to have to start over from step one. Flash SU6-7 in RSD Lite as mentioned in the directions, and follow the directions word-for-word. You're only wasting your own time, not ours.
Q: My phone is stuck at the black green and the root script isn't detecting my phone?
A: You're probably using a USB3.0 port which isn't supported. Move your phone to a USB2.0 port and install the Qualcomm drivers provided in the download.
Q: Why is it taking so long, I think it froze.
A: Just leave your phone alone and get a coffee. Make that three. It's a long process.
Q: Can I install blah-blah ROM?
A: NO! While this is a perma-root, you are unable to disable write-protection, therefore you can't use Safestrap.
Q: Now that I'm rooted, can I unlock my bootloader?
A: SU4-21 was the last system update that worked with Sunshine. Unless you can get in contact with the Chinese middleman, you're out of luck. Sorry.
Q: Why won't my changes to /system persist after a reboot?
A: Unfortunately, no one has managed to circumvent write protection on the device, therefore you can't do anything to /system and expect it to persist unless you do soft-reboots. Sorry.
Q: Can I delete system apps?
A: No, unless you edit the system.mbn and split it into 16mb chunk files. There's no way around this, sorry.
Q: Can I install your Busybox image?
A: I mean if you want a brick, go right ahead. No one's stopping you.
Q: Viper4Android?
A: Which needs Busybox. Again, feel free to proceed at your own risk.
Q: Can I downgrade to SU6-7 if I took the upgrade to SU6-7.2?
A: Yes, you can. There's no magic trick to downgrading to SU6-7, just flash it in RSD Lite.
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Q: Wait, if we can downgrade to SU6-7, why not just downgrade to SU4-21 and unlock our bootloaders?
A: Because you can't. Debating about it on the forums won't magically make it work neither. Nor will complaining about Motorola locking down the devices. You bought an on-contract device that you knew was going to be locked and stock. They also had a developer edition MAXX for sale. If you didn't get it, blame yourself, not Motorola/Verizon.
Q: Can we take the OTA update without losing root?
A: Yes, but you will lose Xposed if you do.(Answered by @DmdStar)

Thanks for the faq @thenameisnigel
Sent from my XT1080 using Tapatalk

yeah thx

Nice one ! Thanks for Viper4Android information. What preset did you choose (battery saving, high/super quality) ?
Actually I don't see what stops you from deleting an app, although it's faster "frozing" it via Titanium for example (paid solution). I removed some files successfully (I should try with apps). Also, did you try installing another ROM ? I didn't take the time to try it but it might work with the python script. You just would have to replace almost all memory blocks, which would take 16+ hours (!!).
I've another question : did someone succeed in installing CF.Lumen ?
Thanks again for the faq
PS : agree with Artimunor just below my post, change colors please !

thenameisnigel said:
Q: Can I delete system apps?
A: No.
Click to expand...
Click to collapse
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
thenameisnigel said:
Yes
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
My original post:
Artimunor said:
Thats the reason i would like to know how to safely alter the image we upload to the phone, to add/remove apps from it.
Is it save to just mount the image on a linux system as a HD and alter the /system directory?
Click to expand...
Click to collapse
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.

Artimunor said:
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
My original post:
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.
Click to expand...
Click to collapse
It's possible if you edit the image like what you're doing. That answer was meant more for people who want to edit /system directly from the device. I'll clarify it.
Sent from my XT1080 using Tapatalk

can i have only root with SU7-6 and locked bootloader?

Deleted.

danger2u said:
can i have only root with SU7-6 and locked bootloader?
Click to expand...
Click to collapse
thenameisnigel said:
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Click to expand...
Click to collapse
Sent from my XT1080 using Tapatalk

thenameisnigel said:
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
ok.
but can i have root with locked bootloader with the method that bricks the phone?

danger2u said:
ok.
but can i have root with locked bootloader with the method that bricks the phone?
Click to expand...
Click to collapse
Yes.
Sent from my XT1080 using Tapatalk

if i restart the phone,the root will remain ?
Busybox can be installed?

danger2u said:
if i restart the phone,the root will remain ?
Busybox can be installed?
Click to expand...
Click to collapse
Only if you put it in the image before you flash it to the phone it seems, if you do it afterwards it does not persist.

another question
can we take the OTA update without losing root?

danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Yes. But you will lose xposed if you installed it.
Sent from my XT1080 using Tapatalk

danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.

Artimunor said:
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.
Click to expand...
Click to collapse
i updated
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
ps: don t update if u want xposed.

danger2u said:
take it the update
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
Click to expand...
Click to collapse
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk

thenameisnigel said:
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I take it the update
i don t tell anyone to update the Droid maxx.

are you referring to losing functionality of a baked in exposed? I am running the crash exploit, with non-baked exposed, on SU6-7.2

Corrupt message,

Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol

No.

Gytole said:
No.
Click to expand...
Click to collapse
Not at all possible yet?

H4X0R46 said:
Not at all possible yet?
Click to expand...
Click to collapse
Still no.

Thanks guys for your responses! Appreciate it! It was a super noob question, but like I said, I own a shamu and it's different. Thanks!

H4X0R46 said:
Hey guys, so I own a Nexus 6 (shamu) not a 6p, but just a curiosity question. I was told that the dm verity for the 6p was in the bootloader and not the kernel, it's built into the kernel on the shamu and the solution is just a custom kernel to remove the message, as for the 6p, is there a known way to remove those messages seeing as it is in the bootloader this time around? Nobody want's to corrupt a bootloader, or you're screwed! Lol
Click to expand...
Click to collapse
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.

dl200010 said:
dm verity is part of the kernel. it can be seen in the linux tree. the bootloader just has a message about being unlocked. i was able to disable dm verity in AOSP when compiling android, without modifying the kernel. just a command in the fstab tells it to verify. the message in the boot loader is just to make sure you know it is unlocked.
Click to expand...
Click to collapse
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.

H4X0R46 said:
So a simple command can disable verity messages in this case? The others in the thread here were saying it's pretty much impossible.
Click to expand...
Click to collapse
No. A simple command does not disable verity, but modifying boot does. The messages that you get about "possibly corrupt" are from the boot loader. If relocked, then it would go away.

It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.

Gytole said:
It lamens terms it is saying "Hey i'm vulnerable! Read what you do before you flash that Galaxy S9 Rom on me!"
I honestly don't mind the message, and its only on screen for 3 seconds...I don't get the big deal.
And you can't compare phones....the Nexus 6 and Nexus 6P....are different phones....they use different everything and google is movong towards a more secure android experience so expect a plethora of corrupt this and broken that messages. Haha
I actually borked my friends Nexus 6 for a good 5 minutes a few months back because I didnt know you had to flash a modified boot and all we did was root it! But lesson learned and not one problem since!
But the message won't go away, it's to tell the next person you sell it to you did stuff to it. That's what she said.
Click to expand...
Click to collapse
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?

H4X0R46 said:
Yea, not so much comparing the phones, just using the Nexus 6 as an example. Yea the 6p is definitely different from the older Nexus models, and I remember someone saying something about an efuse thing you can trip and can't reverse, much like Samsung phones. How does this work? Is it like Samsung where it will always say it's been tampered with forever?
Click to expand...
Click to collapse
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha

Gytole said:
I guess I am very confused at why you're asking this...are you truing to figure out if the message means its corrupt? Because it more than likely isn't...it is just warning of possoble corruption you can has.
And you do lnow fuses can't be fixed once they're blown...you should have answered your own question haha
Click to expand...
Click to collapse
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol

H4X0R46 said:
Yea, the messages i know are just to let you know, the fuse is what i was wondering about. Kind of how the older Galaxy phones, the flash counter was able to be reset with the triangle away app and root, the nexus 6p is permanent? Yea, some noob questions, but it's because I own a shamu and never had to worry about any of this new stuff lol
Click to expand...
Click to collapse
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.

dl200010 said:
No, the Nexus 6P is not permanent unlock. You can easily relock. There is no "unlock counter" or a "flash counter". I have mine unlocked the fuse I have read about elsewhere is still NOT blown. If you do call up google for support and you are unlocked, rooted, and/or custom ROM, then their first trouble shooting will be to download and flash the factory images. If the flashing of factory images does not fix your problem, then they will step up from there. Like replacing the phone. Unlike Samsung.
Click to expand...
Click to collapse
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!

H4X0R46 said:
Cool! So the Qfuse isn't even blown by installing custom files and unlocking the bootloader? I've read other places that people said you can never relock your bootloader, glad that's not true!
Click to expand...
Click to collapse
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.

dl200010 said:
I just used "fastboot flashing unlock", but I think if you use "unlock_critical" it might blow. I am not going to do this.
The "unlock_critical" allows you to flash a custom bootloader and radio. This may help if you want to flash a bootloader without the corrupt message, but it is only visible for a few seconds in booting. Flashing a custom bootloader is very risky. Not worth it for me. Bad bootloader flash or bad bootloader code and no fastboot after, thus no flashing stock bootloader.
Most will only need "unlock" to flash vendor, system, boot, and recovery.
Click to expand...
Click to collapse
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?

H4X0R46 said:
So on the 6p, you need unlock_critical to flash the radio? Doesn't every factory image come with a new radio file? So you may have to blow the qfuse if you want the newest bootloader and radio file?
Click to expand...
Click to collapse
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

AndyYan said:
He means "custom" (third-party/unsigned) ones. Official ones are okay.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Click to expand...
Click to collapse
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol

H4X0R46 said:
Same for stock radio? Yea, I wouldn't even risk flashing a custom Bootloader to anything! Not worth the consequences lol
Click to expand...
Click to collapse
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.

dl200010 said:
Same goes for the radio. I forgot to say that you can flash the factory ones no problem. They are signed.
Click to expand...
Click to collapse
Thanks guys!

Post MHC19l update camera does not work at all

So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.

None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.

Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?

Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!

Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.

Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.

Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys

So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk

and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk

and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?

Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.

naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.

did it flash the vendor?

Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk

and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.

Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk

Is there any way to root OP5 without twrp or unlocking bootloader ??

I dont want to unlock bootloader yet. So i wanted to root the device safely without flashing anything.

You simply can't flash any zips unless on a custom recovery and for that you have to unlock bootloader.
BTW the first thing i did upon getting my op5 was to unlock the bootloader.

"Root without flashing anything."
Sent from my OnePlus 5 using XDA Labs

PrakashGD said:
I dont want to unlock bootloader yet. So i wanted to root the device safely without flashing anything.
Click to expand...
Click to collapse
Why not?

0xTJ said:
Why not?
Click to expand...
Click to collapse
If something goes wrong I may brick the phone

PrakashGD said:
If something goes wrong I may brick the phone
Click to expand...
Click to collapse
You're more likely to brick your phone using a janky and sketchy no-unlocking method than using the documented and manufacturer-recommended method.

0xTJ said:
You're more likely to brick your phone using a janky and sketchy no-unlocking method than using the documented and manufacturer-recommended method.
Click to expand...
Click to collapse
I want to keep my device untouched for some time. Thats why im looking for alternative method to root the device.

PrakashGD said:
I want to keep my device untouched for some time. Thats why im looking for alternative method to root the device.
Click to expand...
Click to collapse
Rooting touches your device just as much. Unlocking the bootloader is like using the key to open a door to get into a building. Trying to do it without unlocking is like using a sledgehammer to break in through the door.

PrakashGD said:
I want to keep my device untouched for some time. Thats why im looking for alternative method to root the device.
Click to expand...
Click to collapse
Impossible, its like wanting to make an omelet without breaking an egg

You can just lock the bootloader again and noone would know you'd unlocked it. One Plus isn't like Samsung!

gee2012 said:
Impossible, its like wanting to make an omelet without breaking an egg
Click to expand...
Click to collapse
Dude ur reference is dope ??

gee2012 said:
Impossible, its like wanting to make an omelet without breaking an egg
Click to expand...
Click to collapse
If there is a security flaw it's possible to root it. It's been happening with phones like sony for ages

B3501 said:
You can just lock the bootloader again and noone would know you'd unlocked it. One Plus isn't like Samsung!
Click to expand...
Click to collapse
Yes but one-click root apps are very unreliable in general and most don`t even work nowadays (especialy system less root). Unlocking the bootloader and flashing Magisk or superSU with TWRP is the best and safest method atm.

gee2012 said:
Yes but one-click root apps are very unreliable in general and most don`t even work nowadays (especialy system less root). Unlocking the bootloader and flashing Magisk or superSU with TWRP is the best and safest method atm.
Click to expand...
Click to collapse
What? I didn't say anything about one-click root apps?!

B3501 said:
What? I didn't say anything about one-click root apps?!
Click to expand...
Click to collapse
Sorry, quoted the wrong user meant the post of @xabierd

Mate, if you don't want to replace your recovery with TWRP, go to fastboot, make sure you have your phone discoverable and use the command "fastboot boot recovery.zip" - recovery.zip being TWRP. This will just boot into TWRP where you can flash magisk or supersu. This won't replace your stock recovery.
You will still need to unlock your bootloader however...

(ASK) Unlocked bootloader warning

hi.. can someone help me ...??
i need to know is there anyway to remove the unlocked bootloader warning on zen max pro m1??
its so annoying, and it makes bootup time longger..
any help would be appreciated...
thank you...

ungi79 said:
hi.. can someone help me ...??
i need to know is there anyway to remove the unlocked bootloader warning on zen max pro m1??
its so annoying, and it makes bootup time longger..
any help would be appreciated...
thank you...
Click to expand...
Click to collapse
If you wish to remove it you have to relock your bootloader otherworldly the warning stays!

ungi79 said:
hi.. can someone help me ...??
i need to know is there anyway to remove the unlocked bootloader warning on zen max pro m1??
its so annoying, and it makes bootup time longger..
any help would be appreciated...
thank you...
Click to expand...
Click to collapse
yes its very annoying

I have also searched for it,
But i think yet its not possible to remove that
Because same kind of thing is also there in xiaomi phones
Showing unlocked at the bottom

I had the Moto G4 Plus before this. You couldn't shave off the boot time, but it could be flashed over using logo.bin. So, no more warning screen.
To be honest, I don't know if something like this exists for X00TD.

Ak-64 said:
If you wish to remove it you have to relock your bootloader otherworldly the warning stays!
Click to expand...
Click to collapse
I know that... But i want to keep twrp.. Twrp will get wipe with stock if i locked it..

ungi79 said:
I know that... But i want to keep twrp.. Twrp will get wipe with stock if i locked it..
Click to expand...
Click to collapse
Yes, it's annoying AF, but for our device as of now there is no script or anything we can flash to get rid of it.
Doesn't affect the boot time though.
For going back to stock part - Lol, he was being sarcastic. If you want twrp, you gotta keep bootloader unlocked and bear those stupid warnings during boot.

akshmau5 said:
Yes, it's annoying AF, but for our device as of now there is no script or anything we can flash to get rid of it.
Doesn't affect the boot time though.
For going back to stock part - Lol, he was being sarcastic. If you want twrp, you gotta keep bootloader unlocked and bear those stupid warnings during boot.
Click to expand...
Click to collapse
Well i think we just have to wait.. Till someone find a way to do it...

Guys, can I root then lock bootloader to stopmthe warning if I don't to use the TWRP anymore but keep the phone rooted?

Has someone found a way to do this?

THREAD CLOSED! If interested in this subject please follow in this already existing thread: https://forum.xda-developers.com/as...removing-unlocked-bootloader-warning-t3841469
@ungi79 XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
...
...
Click to expand...
Click to collapse