Related
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?
Hello!
I have a question, I tried too much ROMs, and now I decide to keep my Stock ROM with a Custom Kernel, like:
Stock ROM: http://forum.xda-developers.com/moto-x/development/rom-firmware-stock-brasil-4-4-4-zip-t2873516
Kernel: http://forum.xda-developers.com/moto-x/development/kernel-zwliew-kernel-r1-t2926315
And for security things, I have bought a Kaspersky Licence to track, block and wipe data, with SMS or WEB commands. But if I got stoled, and the thief knows how to get in the Recovery Mode, he will wipe the ROM and get access to my data in the same way, without the Kaspersky tool.
So I have a question, is there any way to block the bootloader and block the recovery?
I don't have the answers but I can probably give you some good questions to ask.
I don't imagine there's any way to "block the bootloader" if that's what you really meant to type.
First thing you might want to do is flash the stock recovery. You won't be able to flash custom things with it but you can't do much else in stock recovery like you can in a custom one.
If you did want to make changes which required a custom recovery you could already just flash one. Granted, a tech savvy thief could always do the same if they realized that you're unlocked but that would probably weed out the average opportunistic pretty thief.
### There may be risks to this that I don't know but if you wanted to take it a step further I WOULD THINK you could even relock the bootloader. I unlocked via the China middleman so I have my unlock code to use/reuse whenever I want. I think I recall hearing that sunshine will also relock and reunlock the same phone once purchased for that phone? What I don't know is if there's any risk to locking a bootloader with a non stock system.
###
marcelorepavan said:
Hello!
I have a question, I tried too much ROMs, and now I decide to keep my Stock ROM with a Custom Kernel, like:
Stock ROM: http://forum.xda-developers.com/moto-x/development/rom-firmware-stock-brasil-4-4-4-zip-t2873516
Kernel: http://forum.xda-developers.com/moto-x/development/kernel-zwliew-kernel-r1-t2926315
And for security things, I have bought a Kaspersky Licence to track, block and wipe data, with SMS or WEB commands. But if I got stoled, and the thief knows how to get in the Recovery Mode, he will wipe the ROM and get access to my data in the same way, without the Kaspersky tool.
So I have a question, is there any way to block the bootloader and block the recovery?
Click to expand...
Click to collapse
No.
There is no security with an unlocked boot!
One reason THEM don't want it.
See the Philz dev thread (search) for a discussion on this issue.
If you are concerned about security, then flashing a custom ROM/Kernel is the wrong thing to do. You should leave the phone stock, enable device encryption, and also have stock recovery and a locked bootloader.
aviwdoowks said:
No.
There is no security with an unlocked boot!
One reason THEM don't want it.
See the Philz dev thread (search) for a discussion on this issue.
Click to expand...
Click to collapse
But is there any way to lock again my phone? Before a custom ROM/Kernel installed?
Thanks!
marcelorepavan said:
But is there any way to lock again my phone? Before a custom ROM/Kernel installed?
Thanks!
Click to expand...
Click to collapse
No. Because recovery is always accessible.
You can lock your phone at any point, but that isn't going to make it any more secure if you are rooted and/or have a custom recovery installed.
Sent from my Moto X
imnuts said:
You can lock your phone at any point, but that isn't going to make it any more secure if you are rooted and/or have a custom recovery installed.
Sent from my Moto X
Click to expand...
Click to collapse
Hello! Another question!
If a thieft with experience in ROMs/Root and this things get a Normal Moto X Unrooted and Original and Stock. Its is possible he wipe the data, of course...but Its possible to him, get the phone rooted and wipe the data too.
I'm trying to say, a phone with root and unrooted is the same thing about security, because if the Thief have experience, he will do the same thing...a unrooted phone wipe will lost all the datas, a rooted wipe will keep photos and files, right?
Factory reset doesn't care if you're rooted or not. If the phone is locked, unlocking will wipe data. Rooted or not, a factory reset deletes everything. Stock recovery will wipe the emulated SD card as well, where custom recovery doesn't by default, though it still can if you want.
Being rooted makes it easier to pull the data off the phone, but just because one isn't rooted doesn't mean your data is safe.
Sent from my Moto X
I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.
BEDickey said:
I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.
Click to expand...
Click to collapse
Settings --> Security - First thing listed should be encrypt phone.
I know that. I'm saying all that does is restart it to the lock screen, as I said. The phone is not actually encrypted in the process like it should, it just restarts.
With Mofo root, you had to encrypt on an unrooted stock ROM, then flash the rooted ROM after. Are similar also required with CM?
I'm not sure but you can temp disable root in CM by A) Disbaling it in SuperSU app - Uncheck "Enable Superuser" or B) In the settings under developer options - Change "root access" to "disabled". Try that and encrypt then re-enable after
Thanks! I will check it out and report back.
I'm having the exact same problem. I was never able to encrypt running total stock, computerfreek rom, or rremix rom. Device briefly shows the green android, then begins a soft reboot and then a full reboot. I have tried disabling root (both ways) as suggested above. It makes no difference.
Same here, I have the same situation. It seems as though either CM itself or the act of unlocking to bootloader has removed the ability to encrypt your phone. Any advice from people more in the know would be helpful.
In my case, I have never been able to encrypt... even with a totally stock, unmodified, unrooted, unmofo'd, bootloader locked device. Googling around, it seems like a problem where the disk is partitioned in such a way that there isn't the required space left for encryption to initiate. Anything looking like a solution was way over my comfort level (manual repartitioning via terminal), or in the case of some flashable scripts, was outdated.
Question: Did either of you change the format of your /data partition in TWRP to maybe ExFAT or F2FS?
I have never formatted anything.
I think it's one of things you cannot do, since the bootloader is unlocked. IIRC, it must be locked, regardless of the manufacturer. That's why we have the bootloader toggle in dev options.
Sent from my DROID Turbo using Tapatalk
Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.
P_6 said:
Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.
Click to expand...
Click to collapse
This worked for me:
1. Flash back to 100% stock.
2. Encrypt through security settings.
3. Flash whatever you want afterwards. The encryption will be preserved.
I'm currently encrypted and running CF's rom with no issues. A bootloader unlock does not prevent encryption from working.
Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)
P_6 said:
Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)
Click to expand...
Click to collapse
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.
TheSt33v said:
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.
Click to expand...
Click to collapse
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?
P_6 said:
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?
Click to expand...
Click to collapse
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.
TheSt33v said:
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.
Click to expand...
Click to collapse
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.
P_6 said:
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.
Click to expand...
Click to collapse
Weird. You might have to start all over again by going back to stock, and this time either keep the pin or just not deal with encryption.
Hey guys, i lost my phone the other day and thank god no one stole it, i freaked out on how easy it can be to bypass the lockscreen by just entering recovery or bootloader..
I have rooted my phone (no custom recovery yet) but i want to add more protection, is there a way to protect the device from entering recovery or bootloader or any of that kind in case if it got stolen and prevent it from a complete wipe? are there any security modules on xposed?
Encryption?
Sent from my SM-N920T using Tapatalk
I dont want just encryption on data.. I mean look down the hardware keys from force reset, put pass on recovery mode and the bootloader something like that to prevent the wipe..
Not possible. Once you're in recovery it's the base operating system of the phone.
Sent from my SAMSUNG-SM-N920A using Tapatalk
You won't be able to prevent the wipe. But, you can prevent someone from setting up their account after a wipe. It's the Google device protection feature. As long as you have a secure lock screen and are signed in with a Google account, it will be very difficult for most to bypass the log in screen after a wipe.
Sent from my SM-N920T using Tapatalk
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.