Database Develop

Security Issues With Unlocking the Bootloader Without Rooting?

Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?

That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...

Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.

eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.

Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.

eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.

Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.

eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.

Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.

eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?

Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy

Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...

eksasol said:
someguy
Click to expand...
Click to collapse
ok great!

kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.

Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2

pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.

eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader

It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....

pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?

Official Kitkat update from sammy (for Gt-i9295) earth shattering !!!!!!)

THERE IS NO NEED TO DE-KNOX THIS UPDATE
Here is the link http://terafile.co/5884c64311e9

Is the attached file De-Knoxed ?

terisse said:
Is the attached file De-Knoxed ?
Click to expand...
Click to collapse
nope ... wait 2 hours and all the instructions will be here

mythi said:
nope ... wait 2 hours and all the instructions will be here
Click to expand...
Click to collapse
SWEEEEEEEEEETT Thanks:good::good::good::good::good:

people ... After hex editing sbl1.bin (the bootloader) knox isnot loaded on the phone but there is enough code to indicate that knox is coming through a sw update shorlty u guys can flash it with odin safetly , there is no need for long instructions nor anything just load it up and enjoy kk :good:

mythi said:
people ... After hex editing sbl1.bin (the bootloader) knox isnot loaded on the phone but there is enough code to indicate that knox is coming through a sw update shorlty u guys can flash it with odin safetly , there is no need for long instructions nor anything just load it up and enjoy kk :good:
Click to expand...
Click to collapse
Hello mythi,
thanks for debugging.
Can you tell me, if it is possible to flash the 4.2.2 Custom Recovery?
cheers

alirey said:
Hello mythi,
thanks for debugging.
Can you tell me, if it is possible to flash the Custom Recovery?
cheers
Click to expand...
Click to collapse
yes ofcourse flash the latest one by me ... but you need to keep holding volup+home for longer time if you do it the hard way

mythi said:
yes ofcourse flash the latest one by me ... but you need to keep holding volup+home for longer time if you do it the hard way
Click to expand...
Click to collapse
cool
let me summarize:
- your provided rom has a disabled knox bootloader
- CWM 6.0.4.7 installation should work
- SuperSu 1.93 should root
- freezing of the following processes lets knox sw sleep:
KNOX
KNOX Store
KLMS Agent
Knox Notification Manager
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
wright?
thanks again...57min left for rom download. KK i am coming

alirey said:
cool
let me summarize:
- your provided rom has a disabled knox bootloader
- CWM 6.0.4.7 installation should work
- SuperSu 1.93 should root
- freezing of the following processes lets knox sw sleep:
KNOX
KNOX Store
KLMS Agent
Knox Notification Manager
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
wright?
thanks again
Click to expand...
Click to collapse
yap u nailed it

Fast mirror:
https://mega.co.nz/#!XIMl1DDQ!IZeJ2ilX-EacFvzYeWqAVmcFbzedfFXiFvQEvuJm4AI

@Mithy correct me if I'm wrong but I understand that you post the stock ROM without any modification.
The only (but so nice for us) thing you've done is inspecting the code and found that, even if sammy put some trace of Knox for future update, there is NO KNOX BOOTLOADER INSIDE.
Then so far is it possible to act with KK just like with ICS (root, CWM ....) ?

Supersu 1.94 say that Knox is installed on device, and try to isable knox. Success. It works. Rooted.

Thank you very much for this firmware modification.
Sorry noob questions.
1. So if I root with this firmware, Knox warranty bit not going to be tripped? Any precautions how to not activate Knox on this firmware? I just want to have stock Rom without Knox and without root. Or Rom with root ability but without Knox in bootloader.
2. Anyone know what with future updates, if I install this I can in future update to next Android version s without errors/brick? I have German phone.
3. What about warranty if I install this? Does Triangle Away works? If my phone broke should I reset it to factors settings before sending it to Samsung? If I reset it, will Knox be activated in bootloader?
4. Can I downgrade back to 4.2.2? Without tripping Knox?
typed from dark room

What languages does this rom have? Is hungarian included?

ewa12321 said:
Thank you very much for this firmware modification.
3. What about warranty if I install this?
Click to expand...
Click to collapse
I'm still downloading so ....
But on this special point, because you're german, by european law, you're allowed to install any OS on any device without voiding warranty, thanks to microsoft's aggressive politic in 90's about linux on computer.
Europe's not so bad after all :angel:....
I advise you to reset to stock rom anyway if you need warranty support. Do a nice nandroid backup.

SOLVED!
Autorotate won't work for me!
Working after wipe from original recovery, just three buttons combo.

borgwarrior said:
What languages does this rom have? Is hungarian included?
Click to expand...
Click to collapse
Yes, it's included

Thank you very very very very much for this :laugh::laugh::laugh::laugh:
Do you know if there is any way to get root?

dadme said:
Autorotate won't work for me!
Click to expand...
Click to collapse
On my device it was disabled by default. Enabled and it works
Sent from my GT-I9295 using XDA Premium HD app

My wifi is not working and also I don't have root.
Sent from my GT-I9295 using XDA Premium 4 mobile app

Unroot and relock bootloader

I'm currently considering unrooting my turbo and relocking the bootloader but am not completely sure how. Looking for confirmation that I'll be doing it right.
1. Flash the fix to remove the unlocked bootloader warning
2. Uninstall all root apps (xposed and superSU)
3. Flash stock recovery
4. Fastboot oem lock
I'm already on the stock mm rom and I think I might have to flash a stock bootloader before the stock recovery, but not sure.
Thanks for any help.

Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
subprime said:
1. Flash the fix to remove the unlocked bootloader warning
Click to expand...
Click to collapse
THAT should have already been done, when you first unlocked the bootloader.

ChazzMatt said:
Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
Click to expand...
Click to collapse
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?

subprime said:
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?
Click to expand...
Click to collapse
In the beginning you could only use Sunshine one time per phone. I think some others have locked and unlocked, but I'm not sure the process. I think you have to contact Sunshine team? Others can answer if they remember how to do it.
Can you use Magisk to hide root? It seems to work with Android Pay and other stuff.

I'll take a look and give it a shot. Phone has to be encrypted too and from what I read I'm pretty sure I have to unroot for that.
Thanks

My phone is encrypted, rooted with Magisk, and I use Outlook for work

Bootloader logos to replace unlocked warning:
https://forum.xda-developers.com/showthread.php?p=72047829
Choices of TWRP or ADB.
I'm currently using the Dark Google ATAP.

TheSt33v said:
My phone is encrypted, rooted with Magisk, and I use Outlook for work
Click to expand...
Click to collapse
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).

subprime said:
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).
Click to expand...
Click to collapse
Lame. Well hopefully Magisk can work its magic...sk.

Software Install Failed

So I just got the new version update ( I think it's 8.0 ). I download it through the "System Update" and then it requires me to restart to install the update. It then get to the installation but when it gets to 1% I get an error: "Software Install Failed". I then boot my phone back and it requires me to download the whole update again ( 0.95 GB ) every damn time. I already tried updating 3 times but it still fails at 1%.

Are you rooted or did you modified something else?
If yes, remove the root completely with the tutorials of your root method (the root makers always releasing a tutorial how to remove) and relock your bootloader again (WARNING: FACTORY RESET!!!).
After this, you should be able to install the update.

Jannomag said:
Are you rooted or did you modified something else?
If yes, remove the root completely with the tutorials of your root method (the root makers always releasing a tutorial how to remove) and relock your bootloader again (WARNING: FACTORY RESET!!!).
After this, you should be able to install the update.
Click to expand...
Click to collapse
Nope no root or any modification, I still have my warranty

Then use your warranty
Anything the XDA community can help you will cause that you need to unlock your bootloader - without unlocking, there's no solution without official Huawei methods.

Jannomag said:
Then use your warranty
Anything the XDA community can help you will cause that you need to unlock your bootloader - without unlocking, there's no solution without official Huawei methods.
Click to expand...
Click to collapse
Okay thank you for the help!

The only thing you really can do is a factory reset - this is also the only thing you can do without losing any warranty. And this is also the only thing the Huawei support will tell you to do.

Jannomag said:
The only thing you really can do is a factory reset - this is also the only thing you can do without losing any warranty. And this is also the only thing the Huawei support will tell you to do.
Click to expand...
Click to collapse
Thing is I have plenty of data and I don't want to bet it unless it's 100% going to work
What about "Firmware Finder"?

BatedWaif said:
Thing is I have plenty of data and I don't want to bet it unless it's 100% going to work
What about "Firmware Finder"?
Click to expand...
Click to collapse
You can try it with their DNS services, but if the firmware Huawei is providing you won't install, it can also be a problem with your phone.
And there's no 100% safety that you won't lose all your data.
If you send the phone to Huawei you'll also lose everything.

Jannomag said:
You can try it with their DNS services, but if the firmware Huawei is providing you won't install, it can also be a problem with your phone.
And there's no 100% safety that you won't lose all your data.
If you send the phone to Huawei you'll also lose everything.
Click to expand...
Click to collapse
Okay I did that and now I have 8.0. I just hope it has not void my warranty or something. Thanks again for your help!

Jannomag said:
Are you rooted or did you modified something else?
If yes, remove the root completely with the tutorials of your root method (the root makers always releasing a tutorial how to remove) and relock your bootloader again (WARNING: FACTORY RESET!!!).
After this, you should be able to install the update.
Click to expand...
Click to collapse
yes my one is modified and i don't know how to remove the modification.

Then you need to do a factory reset if you want to remove your modifications.

Unlocked Bootloader = No Fingerprint

Fingerprint on this device is disabled after i unlocked bootloader, I tried complete wiping the device multiple times as i thought this was my own fault since i had setup the device prior to unlocking bootloader. No dice.
I thought maybe that a wipe would clear the fingerprint cache or something and make it work.
After locking the bootloader the reader starts working again.
Was this supposed to be the expected behaviour?
I refuse to believe that they would completely disable it system wide instead of just preventing payments etc like normal.
As a side note, transferring user data from an old phone is also broken by bootloader unlock, errors out with "something went wrong" when hitting the copy button to start the transfer.

Just as another side note, the system partition cannot be erased with fastboot either, access denied error even with unlocked bootloader. I figured this out while trying to get my fingerprint reader working. I tried multiple commands and also mfastboot instead of android sdk fastboot

Good news BL is unlockable, bad news FP scanner gets disabled. How about unlocking the BL, rooting the phone with Magisk, and then relocking the BL? Will this work? I haven't got the phone yet, it's arriving next week. Thanks for sharing your findings.

I haven't had a chance to try that. This phone is now my daily driver and I'm working for the next few days so I won't be able to get around to trying until then. I'm sure it wouldn't work though because I believe the device wouldn't boot after the bootloader was modified since locking the bootloader after installing magisk would probably not work.

Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/

darkdaemon32 said:
Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/
Click to expand...
Click to collapse
Certainly looks too risky

Hey, that's weird. I unlocked BL, flashed magisk and my fingerpring works flawlessly.

Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!

Jaysmith696 said:
Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!
Click to expand...
Click to collapse
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.

rafikowy said:
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.
Click to expand...
Click to collapse
You're the best! Thank you so much

Jaysmith696 said:
You're the best! Thank you so much
Click to expand...
Click to collapse
Sorry but unfortunately I won't be able to prepare instructions tonight. Too busy before holidays. Will be back on 25th of Sep. But what can I say is that procedures to "unlock bootloader", "magisk" and "xposed" are very common for many devices (including moto one zoom) and can be easily found in the internet.
btw: PPH29.59-34 software update has just arrived (I live in Poland).

rafikowy said:
I unlocked BL, flashed magisk and my fingerpring works flawlessly
Click to expand...
Click to collapse
Model №? FW Version?
OP, did you try Magisk?

I did not have a chance to try magisk as I was only testing unlocking to see if anything broke. And whenever I couldn't set it up with fingerprint I relocked and wanted to wait to see if others have the same issue. I'm on this fw https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?

You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Jaysmith696 said:
Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?
Click to expand...
Click to collapse

darkdaemon32 said:
You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Click to expand...
Click to collapse
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock ?
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light ?

Jaysmith696 said:
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light
Click to expand...
Click to collapse
I'm having the exact same issue after unlocking bootloader. I didn't modify anything at all and still my phone's lock function is completely disabled. Only way I could fix it was going back to stock and re locking bootloader. I'm currently without root or any modifications because of this. I'm also waiting on a fix

Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.

This may be where my issue is. I had setup the phone and registered my fingerprints prior to the unlock. Im guessing that they are being stored somewhere that I cannot wipe such as /system or inside an enclave chip etc. Because the only partition I couldn't manually use an erase command for was /system as I was getting access denied error. I may get around to trying the Lenovo phone tool and/or removing fingerprints first to see what happens. I just need to find the time to mess with it.

crubbish said:
Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.
Click to expand...
Click to collapse
I don't know why you've got figerprint and everybody's not. I don't have one either. This is also a problem with phones from other manufacturers.
Would you mind seeing who the fingerprint scanner manufacturer is?
I have Goodix.
Maybe it depends. Or maybe the system will shutdown it after unlocking the bootloader.