Hi my Motorola One Zoom is rooted with Magisk and I seen the push notification for the Sept Security Update, will my device go into a BootLoop if it auto installs?
Your help is appreciated ??
Jaysmith696 said:
Hi my Motorola One Zoom is rooted with Magisk and I seen the push notification for the Sept Security Update, will my device go into a BootLoop if it auto installs?
Click to expand...
Click to collapse
OTA will load but not install. Because the system was modified.
Does the fingerprint work?
ilia3367 said:
OTA will load but not install. Because the system was modified.
Does the fingerprint work?
Click to expand...
Click to collapse
Hey thanks for your feedback, I was scared for a moment lol. Unfortunately, my fingerprint, pattern, pin, password screen lock features do not register.
Before I unlocked Bootloader/rooted, I had a fingerprint + Pin setup and now it all is not working. Didn't know I had to clear my lock screen before unlocking bootloader and rooting.
I'm still currently trying to find out how to maybe go Into the phone root directory and delete some cache if it stored somewhere.
I tried deleting my lockscreen_settings.db and no luck.
I really don't want to flash stock firmware, unroot and relock bootloader
Does your fingerprint work or any lock screen feature at that?
Jaysmith696 said:
Does your fingerprint work or any lock screen feature at that?
Click to expand...
Click to collapse
No
ilia3367 said:
OTA will load but not install. Because the system was modified.
Does the fingerprint work?
Click to expand...
Click to collapse
That's NOT TRUE! If you follow these instructions, OTA can be applied normally... Magisk DOES NOT TOUCH System partition btw...
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Related
Im running marshmallow, an interesting problem had popped up. On a fresh boot I get "unable to use fingerprint enter PIN"
Once I do this the finger print scanner works fine, any suggestions on how to fix this?
First unlock after fresh boot always requires pin or pattern unlock.
Sent from my LG-H901 using XDA Free mobile app
evo4g63t said:
Im running marshmallow, an interesting problem had popped up. On a fresh boot I get "unable to use fingerprint enter PIN"
Once I do this the finger print scanner works fine, any suggestions on how to fix this?
Click to expand...
Click to collapse
Solution: http://forum.xda-developers.com/xposed/modules/mod-fingerprint-enabler-t3411066
sure, use the solution of user fixxxer102, that works fine...you need to have xposed installed, by this means you need root and perhaps unlocked bootloader with TWRP installed too!
sun_is_shinning said:
sure, use the solution of user fixxxer102, that works fine...you need to have xposed installed, by this means you need root and perhaps unlocked bootloader with TWRP installed too!
Click to expand...
Click to collapse
He has t-mobile unit so he`s able to unlock bootloader and root his device.
I wasn't aware this is normal behavior so really don't mind it just thought I caused it.
Im a little hesitant to use xposed framework right now.
Thanks guys.
evo4g63t said:
I wasn't aware this is normal behavior so really don't mind it just thought I caused it.
Im a little hesitant to use xposed framework right now.
Thanks guys.
Click to expand...
Click to collapse
sure you need to be!
if you dont have the H960A international you cant unlock your bootloader, i am sure you can root your phone and use flashify to try install xposed and fingerprint moldure, all you need is be patient and everything will be good!
Hey there
I hadd my j5 500fn version for a month its on android lollipop 5.1.1
I tried to root it yesterday and it wasnt that nice
I tried rooting by removing google account and enable usb debugging mode and rooted using the odin method with cf root file
As soon as it finished it rebooted with a yellow "set warranty bit:kernel" message on left top of the device name and it all went fine and root checker said it was rooted and could use all root apps but then i tried adding the google account again and restarted my device and then got the custom binary blocked by frp error
I solved that error by flashing the official stock rom again and then i tried rooting again and got the same problem again
It seems like i cant root with a google account and without it i cant install any google play apps
Any suggestion???
Amir3022 said:
Hey there
I hadd my j5 500fn version for a month its on android lollipop 5.1.1
I tried to root it yesterday and it wasnt that nice
I tried rooting by removing google account and enable usb debugging mode and rooted using the odin method with cf root file
As soon as it finished it rebooted with a yellow "set warranty bit:kernel" message on left top of the device name and it all went fine and root checker said it was rooted and could use all root apps but then i tried adding the google account again and restarted my device and then got the custom binary blocked by frp error
I solved that error by flashing the official stock rom again and then i tried rooting again and got the same problem again
It seems like i cant root with a google account and without it i cant install any google play apps
Any suggestion???
Click to expand...
Click to collapse
Hey any help would be appreciated there many apps i use which require root
Hey there any help ??!
Have you enabled OEM Unlocking in Developer Options?
I didnt check that
Al i tried was removing my google account and enabling usb debugging
es0tericcha0s said:
Have you enabled OEM Unlocking in Developer Options?
Click to expand...
Click to collapse
I would try that but ate there any risks of unrepairable bricks or boot loops ??
Amir3022 said:
I would try that but ate there any risks of unrepairable bricks or boot loops ??
Click to expand...
Click to collapse
Not from enabling that option, no.
es0tericcha0s said:
Not from enabling that option, no.
Click to expand...
Click to collapse
So di you suggest teying to root with oem disabled??
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
es0tericcha0s said:
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
Click to expand...
Click to collapse
Ok i will try that and tell you the results
es0tericcha0s said:
?
The question was whether you have enabled OEM unlocking in the development options. If your phone has this option, it must be enabled for you to load a custom recovery that's used with auto root to root, and then it will flash back the original recovery.
Click to expand...
Click to collapse
I just tried rooting with oem enabled but its the same still getting the yellow set bit warranty:kernel message on startup
Amir3022 said:
I just tried rooting with oem enabled but its the same still getting the yellow set bit warranty:kernel message on startup
Click to expand...
Click to collapse
That part doesn't mean anything. Does root still work?
es0tericcha0s said:
That part doesn't mean anything. Does root still work?
Click to expand...
Click to collapse
It works but as soon as i enter my google account and restart i get the blocked by frp error
Odd. I've rooted dozens of Samsung phones and have not come across this. If you are already logged into Google and then enable OEM unlocking and then root, does it still get blocked?
es0tericcha0s said:
Odd. I've rooted dozens of Samsung phones and have not come across this. If you are already logged into Google and then enable OEM unlocking and then root, does it still get blocked?
Click to expand...
Click to collapse
If i try rooting without removing my google account i get ared failed message while rooting with odin
I also realised that knox flag is tripped at 0x1 could that be tbe problem
Please post a link to the guide you are using.
es0tericcha0s said:
Please post a link to the guide you are using.
Click to expand...
Click to collapse
I dont use a guide to do it i just tried this same method on my old j1 and it worked but ut doesnt seem to work here
Here it is:
Remove google account
Enable oem unlock
Turn off mobile and put it on download mode
Flash the cf auto root with odin
Mobile turns on and it root automatically then reboots
A yellow set bit warranty: kernel message in top of the screen
Until now all is fine root works fine and all but as soon as i enter my google account and reboot i get the custom binary blocked by frp error and have to reflash the official rom again to get it to work
Amir3022 said:
I dont use a guide to do it i just tried this same method on my old j1 and it worked but ut doesnt seem to work here
Here it is:
Remove google account
Enable oem unlock
Turn off mobile and put it on download mode
Flash the cf auto root with odin
Mobile turns on and it root automatically then reboots
A yellow set bit warranty: kernel message in top of the screen
Until now all is fine root works fine and all but as soon as i enter my google account and reboot i get the custom binary blocked by frp error and have to reflash the official rom again to get it to work
Click to expand...
Click to collapse
You might not be using the right CF package. Just try TWRP + SuperSU zip method instead.
es0tericcha0s said:
You might not be using the right CF package. Just try TWRP + SuperSU zip method instead.
Click to expand...
Click to collapse
I will tey to search for a guide to that method and tell you the results
http://forum.xda-developers.com/gal...overy-twrp-2-8-7-0-samsung-galaxy-j5-t3219901
http://download.chainfire.eu/supersu-stable
Make sure to boot into TWRP before it boots into the OS to flash SuperSU.
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
thanks, it worked for me. appreciate.
Your welcome.
What did u even use to root?
What build is this for?
It works with me....Thank you so much.
this works also on 320fn?
fraizzo said:
this works also on 320fn?
Click to expand...
Click to collapse
Sadly not
JustAnotherAndroid said:
What did u even use to root?
Click to expand...
Click to collapse
I used magisk
Sands207 said:
What build is this for?
Click to expand...
Click to collapse
I don't remember
Is this process can unlock the phone from sprint ?
No, call sprint, then ask to unlock
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
Simply turning off usb debugging will not throw your phone into a boot loop normally unless ou had some bad hardware or custom settings.. Only time ive seen that happen is by using data from other models. Easy way to get past it is to just take out your battery for a bit, replace it then boot into upload mode. Next youll have to try various combos releasing the buttons and presing again quickly to get back to the download mode. Alternatively boot into TWRP/STock recovery, use AT+ Commands or use a application that will boot back.
Awesome you found a little trick to simplify it ! Keep it up!
EDIT: Ohh i see.. you are on a custom rom / binary? I still have yet to have this happen but to a J700 with SynexOS on it.. Ill give this a try.
Hi,
sorry up front if this is a redunant question but I've locked my phone with FP and pin/pattern on MIUI. After switching to LOS the boot pattern is still active. Wiping /data with TWRP didn't help. How can I remove/delete it permenantly? Any hints/links? I couldn't find anything useful using the search though .
saski4711 said:
Hi,
sorry up front if this is a redunant question but I've locked my phone with FP and pin/pattern on MIUI. After switching to LOS the boot pattern is still active. Wiping /data with TWRP didn't help. How can I remove/delete it permenantly? Any hints/links? I couldn't find anything useful using the search though .
Click to expand...
Click to collapse
Theres a zip to remove lockscreen passwords, after you redo ur pattern and whatever, enter fingerprint and you need to reenable smart lock in trusted agents, because it won't show otherwise.
This is also the same thing just manually
Patch rom
Via
Orangfox or pitchblack recivery during flashing
Mooatreides said:
Theres a zip to remove lockscreen passwords, after you redo ur pattern and whatever, enter fingerprint and you need to reenable smart lock in trusted agents, because it won't show otherwise.
This is also the same thing just manually
Click to expand...
Click to collapse
could you pinpoint me to that zip please?
saif hussain said:
Patch rom
Via
Orangfox or pitchblack recivery during flashing
Click to expand...
Click to collapse
So orange fox recovery can actually erase the pattern? can I do this via hotboot since I use TWRP?
saski4711 said:
could you pinpoint me to that zip please?
Click to expand...
Click to collapse
Follow the video its easy and does the same, i tried uploading it and it dint work
Ok guys I managed to do this with TWRP by formatting/wiping everything. Was going to install another custom ROM anyway so I didn't mind the data loss.
Anyway thx for your help! :highfive:
saski4711 said:
So orange fox recovery can actually erase the pattern? can I do this via hotboot since I use TWRP?
Click to expand...
Click to collapse
Switch to orange fox
Its a easy wau
Hello there,
I had rooted my phone before the official TWRP came for POCO with the support to decrypt encryption. I used to flash DFE then which disabled the encryption on my phone. I use the Official TWRP now which support decrypting the phone. I want to enable encryption again for my POCO F1 to make the files inaccessible in case my phone is lost/stolen. How do I enable encryption on my phone without formatting the data?
Edit: I just ran getprop ro.crypto.state in shell and it says encrypted. I am confused. If my device is encrypted then why does not TWRP ask me for a password to decrypt my phone when I boot into recovery? Please help.
It is encrypted with the default android key right now, thats why you got that message.
To encrypt with your private key, go to Developer options and Encrypt device using lockscreen password(at the bottom). This is in MIUI 11
Nik2424 said:
It is encrypted with the default android key right now, thats why you got that message.
To encrypt with your private key, go to Developer options and Encrypt device using lockscreen password(at the bottom). This is in MIUI 11
Click to expand...
Click to collapse
Got it. Thanks! Will there be any issue if I enable it now? I am on stock miui 11.0.8.0 with bootloader unlocked and rooted with Magisk. I just don't want to lose any data.
geekwithlens said:
Got it. Thanks! Will there be any issue if I enable it now? I am on stock miui 11.0.8.0 with bootloader unlocked and rooted with Magisk. I just don't want to lose any data.
Click to expand...
Click to collapse
Sorry can't help you there. I'm running locked bootloader with 11.0.8.0. It worked perfectly here without losing data but I have no idea about unlocked bootloader.
I guess you can just make a full backup and give it a try. Best of luck, let me know how it goes!
REFLASH the desigred vendor image and reboot you will be encrypted on your next boot
usually data will not be deleted but its always best to take backup
YasuHamed said:
REFLASH the desigred vendor image and reboot you will be encrypted on your next boot
usually data will not be deleted but its always best to take backup
Click to expand...
Click to collapse
There is an option to enable encryption in the settings as mentioned by Nik2424 "To encrypt with your private key, go to Developer options and Encrypt device using lockscreen password(at the bottom). This is in MIUI 11"
I am attaching the screenshot of the same with this post for your reference. Can I enable this setting without losing data and root?
Nik2424 said:
Sorry can't help you there. I'm running locked bootloader with 11.0.8.0. It worked perfectly here without losing data but I have no idea about unlocked bootloader.
I guess you can just make a full backup and give it a try. Best of luck, let me know how it goes!
Click to expand...
Click to collapse
It worked even with unlocked bootloader and root. Thanks!
geekwithlens said:
It worked even with unlocked bootloader and root. Thanks!
Click to expand...
Click to collapse
Glad to hear! Enjoy the extra security
Nik2424 said:
Glad to hear! Enjoy the extra security
Click to expand...
Click to collapse
Any idea how secure is this full disk encryption of android?