Database Users

Bootloader unlocked - remove untrusted warning?

Apologies if this has been covered anywhere; I couldn't find it. When the bootloader on the Mediapad is unlocked a 'warning: bootloader unlocked" screen appears on boot. Is it possible to remove/hide/replace this warning while also keeping the tablet rooted?

Sorry mate, this is not possible. Similar to Samsung boot message when knox is tripped.
Regards

On the Moto X Style a flashing a new boot.img with it removed fixed the problem, I don't know if there is anything similar?

For now we have no sources to make a boot.img for M3.

Well... damn, didn't greatslon provide a boot.img? Although I think it was a complete custom make rather than an adaptation of stock.
Cheers anyways; hopefully a solution will appear in the future.

Will relocking it keep the root?

[DISCUSSION] Re-locking Bootloader w/ Custom OS

While I am an advocate for device customization and modifications, I also believe there is an inherent need for locked bootloaders. When we unlock a BL and leave it that way so we can run custom ROMs, root etc, we sacrafice the security it provides allowing our devices to be tampered with or redistributed after a theft. I've seen the PSA advising people not relock their bootloaders on anything except stock. That is entirely true for Verizon and EE pixels that were never intended to be unlocked in first place. However I believe its entirely possible to boot properly self signed images on unlockable devices after re-locking.
Now, I'm not saying we should go around re-locking bootloaders with custom firmware installed there's a process. I've done a bit of reading on verified boot. I am interested in utilizing the "YELLOW STATE" so we can run self signed boot images using an "embedded certificate" along with dm-verity disabled. The problem is how can we self sign our boot images allowing boot to continue without compiling from source?
https://source.android.com/security/verifiedboot/verified-boot.html
https://mjg59.dreamwidth.org/31765.html
I found some information & maybe a more experienced DEV can shed some light on if its possible with our Pixel devices. That's really the goal of this thread, to start a discussion which I think is extremely important & hopefully turn into a guide or tool. We shouldn't completely sacrafice security to utilize root or custom ROMs. On my N5X I have a locked bootloader and modified boot/system with Allow OEM unlock disabled. Difference with our Pixels and Nougat BLs is verified boot is strictly enforced.
Please excuse me if this thread seems jumbled or all over the place. I really do want help with this idea tho to help inform and keep us secure. Any input is appreciated.

Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.

I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk

milan187 said:
I still wouldn't do this. What's the point? You will still pass safety net with custom kernel.
As for security you, your device still needs to be decrypted to use TWRP. It should still be as secure. I guess someone can wipe your device if they get ahold of it but that's not really a security risk.
Risk is still huge locking your device with a custom OS.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.

Which risk is greater. The risk of losing an unlocked device and it falling into the hands of someone that knows what to do or bricking it relocking it.
I vote the latter.

Its not re-locking that bricks... Its disabling the allow OEM unlock in dev options & screwing with stuff afterwards that may cause a bootloop. As long as you have a signed boot image in place with TWRP or stock recovery that uses your own keys the risk is minimal.
Simple rule... With a locked boot loader on a device where verification is strictly enforced always leave that option ticked if modifying anything.
I'm sorry but people are misinformed. Locking the boot loader doesn't brick if you have a custom ROM in place any more than a stock ROM. Its screwing with things or using a poorly dev'd ROM. If you are like me and can set something up the way you like once and not screw with it you'll be fine. If you do wanna screw with something remember to check allow OEM unlock in dev opts. Don't uncheck until you're 100% sure. It really is that simple.

If you are leaving the toggle open what have you accomplished when it gets stolen? They just issue the fastboot command to unlock it. Yea, it wipes data at that point. But I honestly can't think of anything on my phone that is confidential.

When I'm out n about and using my phone normally (i.e. not modding, flashing etc) I put the toggle to off. If I'm planning on changing anything I toggle it back on & if something causes a bootloop (most probably user error) I can recover. I don't think most people who steal phones care about data either but I keep a lot of keys, passwords etc to networks in my devices storage. I admit its not for everybody, just a way to be more secure and protect a $700+ investment. My phones bootloader isn't just locked, its locked with a persistent root ssh backdoor integrated into system so I can maintain control in the event.

want to re-lock my boot loader ?
Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
---------- Post added at 10:57 AM ---------- Previous post was at 10:21 AM ----------
sally76 said:
hey,
I as well as plenty of others thought I was clever unlocking it as I mainly wanted to unlock it from EE UK network , its not been touched since ,no custom rooms or root but after reading people are trying to Re-lock it and getting bricked im too scared too try lol its only phone ive got ? Appreciate any help please x
Click to expand...
Click to collapse
Sorry Duhhhh !! Custom u said lol

Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10?
(Or does anyone else know?)
PS: Sorry everyone for pumping such an old thread

nullstring2 said:
Geofferey, Do you happen to know if these commands are still right with LOS 17.1 / Android 10
Click to expand...
Click to collapse
Unfortunately no. Now there is avbtool and the process is actually a bit more complicated. Somebody wrote a guide on how to use it externally for another device but I couldn't even follow. I actually find it easier to get the sources for whatever ROM it is I'm trying to sign and set the signing params in config before build.
Here is the guy who did it usually avbtool externally
https://forum.hovatek.com/thread-32664.html
Many instructions here
https://android.googlesource.com/platform/external/avb/+/master/README.md

Geofferey said:
...but I couldn't even follow. /QUOTE]
Well, thats an intimidating introduction, but I'll take look.
That guide appears to be talking about mediatek CPUs which makes it a little confusing.
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse

nullstring2 said:
Any hint on how to get the vbmeta signing key for the google pixel?
Click to expand...
Click to collapse
If you mean how to make your own key to perform signing then
Code:
openssl genrsa -des3 -out avb.pem 2048
If you're asking how to get the same key that Google used to sign vbmeta, it ain't ever gonna happen.

Geofferey said:
Well if anybody is interested in re-locking their boot loader with a custom ROM and kernel in place I basically figured out how
Refer to this post
If anybody plans to attempt this and has ANY questions or concerns regarding re-locking their bootloaders in a custom state please don't hesitate to post here. I successfully re-locked my bootloader with custom ROM and Kernel. I also modified TWRP in my kernel to only start via locked down adb with key access. This allows my pixel to be highly secure and still recoverable. Might start a new post highlighting my proceedures and research on this subject.
Click to expand...
Click to collapse
Is there ANY way to do this on Xperias or LGs?

Geofferey said:
It has nothing to do with passing safety net. TWRP can only access the data after the pin is input, true, but leaving a device with an unlocked boot loader leaves the ability to flash modified boot images (a huge attack vector). This is to keep your device yours if it falls into a theives hands. You can not have device protection features on a unlocked Allow OEM unlock device. You're right there is risk but being careful can alleviate the risk. I do this because I want my phone to be a trackable paper weight if somebody takes it. I have established my own chain of trust outside of googles. I have even modified my TWRP side of boot.img to only start with my PC using adb-keys.
Click to expand...
Click to collapse
It has ALL to do with safetynet/play integrity.
I wouldn't care to leave my bootloader unlocked otherwise.
But I want a rom that passes all security standards without "tricks".

Noob flashing doubts

Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk

Belotto said:
Guys,
I have some very noob questions about flashing that I would like to solve :
1) is normal that fastboot connection works only after setting the device for "allow own unlock" and "USB debugging"?
2) I might flashing my devices without unlocking the bootloader? And what about flashing original firmwares from Motorola?
(I ask because my bootloader is locked under status "2")
2) I tried to flash my device and, despite of several "preflashing" errors, my device still showing status 2 on bootloader, but it started showing that "unlocked bootloader warning" when it starts, is that normal? How to solve it?
3) I might flashing an older firmware (update September ) than I already have in my device (December)?
4) what is the function of recovery mode on bootloader ? I
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
OK...My first and main recommendation is DO NOT start trying to flash, mod, or do anything outside of using the phone as intended yet. These questions show that you have very limited knowledge on these subjects and if you continue as is, you will most likely get yourself into a bind you can't get out of, such as hard bricking your device.
Questions 1 and 4 are Bootloader/Fastboot/Rooting 101 topics. Until you have read up thoroughly on these, please don't think about proceeding. The rest of your questions have been answered here in the forums. I can't stress this enough: RESEARCH, READING, AND READ SOME MORE!!! No one here is obligated to help you fix any mess you get into so you need to be able to help yourself first. If you have attempted to fix an issue, and can give some details on what has been tried, you will find that most likely, there will be some who will step forward to assist, but most will not rehash a full step by step of everything.
Please do not think I am trying to blow you off. I am merely trying to prevent you from creating a problem that cannot be fixed. Having at least a basic working knowledge of how FastBoot, Bootloader, and flashing ROMs work on this device is a must. But I will answer your question 3: Do not under any circumstances try to "downgrade" your stock rom on the phone to a previous security update. This does create major issues.

@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.

dzidexx said:
@Belotto
2. Only upper/the same version of stock rom.
Status code 2 - locked by user. Did you buy used phone?
4. Recovery mode(stock, 3e) is for factory reset f.e.
Click to expand...
Click to collapse
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Sent from my XT1575 using Tapatalk

Belotto said:
I haven't. I have unlocked , used custom roms for a time and flashed stock and locked again before. Did it just following to guides available here.
In that time I did not have any trouble doing that lol
Click to expand...
Click to collapse
Just in case you are not aware, having an unlocked bootloader does not prevent you from taking OTA updates. You can just leave it unlocked. The unlocked bootloader warning doesn't bother me so I just ignore it.

If you just wanna get rid of bootloader warning then look at
https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Make sure you are on stock(software​ status: offical)
You will recieve the ota

Thanks all you guys.
Despite of some strange things, I could take out the warning logo.
Now, its "oficial", status "2" and no warning. So I can sell it without discussion.

Is there a way to unlock bootloader yet? [TA-1021 variant]

I've come across this blog: "unlockbootloader .org/tutorial/nokia-6"
It's looked okay but I still very doubt it. This kind of question doesn't received an answer on Nokia phone sub-website, runs by HMD, so I'm posting here.
Also, are there any work around with this phone or you and me will have to wait HMD move first?
Thanks.

I might have misunderstood something, but isn't the bootloader unlockable directly from developer options?
Clicking it gives an usual warning why you shouldn't do it, and asks confirmation. I haven't actually proceeded further because I have no need to unlock it currently..

Zuikkis said:
I might have misunderstood something, but isn't the bootloader unlockable directly from developer options?
Clicking it gives an usual warning why you shouldn't do it, and asks confirmation. I haven't actually proceeded further because I have no need to unlock it currently..
Click to expand...
Click to collapse
Yes, you're misunderstood this thing. The unlock bootloader option is there in developer options and there that's too in fastboot, it'll give you a FAIL error message if you choose it.
If you weren't interested in unlock Nokia 6, why are you comment on this topic?

Unlock bootloader?

I tried everything to unlock bootloader in Black shark 2 Global Version i enabled OEM unlocking on the developer options and then tried fastboot flashing unlock and fastboot oem unlock with adb, and the "error says unlock is not allowed on device has sales on market!", we need to unlock the bootloader there is a post in this forum who have patched the boot.img, so if the boot.img is correct unlock the bootloader is the last step to finally root the Black shark 2.
Any ideas?

There's a link to a forum about the black shark 1, where they encroached the same issues, error message you've described. A user has included instructions on how to bypass/get round it with photos in the post. But it only worked with the global ROM. And it's a different devise but might be worth looking at if you want as much info as possible that might help.
Before you do anything an brick your devise tho, I would recommend an air of caution.
I will pm you the link because I don't know if linking other sites is against the rules of the forum

Ash180287 said:
There's a link to a forum about the black shark 1, where they encroached the same issues, error message you've described. A user has included instructions on how to bypass/get round it with photos in the post. But it only worked with the global ROM. And it's a different devise but might be worth looking at if you want as much info as possible that might help.
Before you do anything an brick your devise tho, I would recommend an air of caution.
I will pm you the link because I don't know if linking other sites is against the rules of the forum
Click to expand...
Click to collapse
Thanks, but i tried that also and nothing worked .