Develop Bugs

How to Root my new Moto Z2 Play?

OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!

Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.

First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.

WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.

pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.

The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.

Can I flash project treble?

Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky

as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture

Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.

bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further

Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?

bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB

bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com

Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.

bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?

Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.

bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms

Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.

bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?

Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.

I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.

Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help

bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?

Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(

bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?

Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.

Question Help me understand GIS for Xperia 10 III

I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.

wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.

How To Guide A23 Unlock Bootloader and Root guides with Video

This is not my work, this simply was found and done by others, so all credit to them
Warning Unlocking and rooting your device is not for everyone, and you risk damaging your device so do it at your own risk.
saw several people asking about, so he is the methods.
to unlock boot loader
to root
video
text Guide by Juhn Wu (Magisk creator)
https://topjohnwu.github.io/Magisk/install.html

Still no any other alternative OS?
Any idea what to install instead of samsung OS?

Rupdabe-GalaxyS6EdgePlus said:
Still no any other alternative OS?
Any idea what to install instead of samsung OS?
Click to expand...
Click to collapse
nothing A23 specific that i know of, but you can try GSI roms

theduke7 said:
nothing A23 specific that i know of, but you can try GSI roms
Click to expand...
Click to collapse
Tnx

will this root method work on the boost variant?

this.guy.lol said:
will this root method work on the boost variant?
Click to expand...
Click to collapse
Nope, any Samsung phone that's sold in the US aka having the letter U or DL "not too sure about ones with U1" cannot be rooted due to having a locked down bootloader and no OEM unlock option, it's been like this ever since the S6 back in 2015. an exploit for the SM-A236U and the SM-S236DL would need to be found to even get close to rooting.

this method works. BUT......
i can root my phone. magisk works fine, but apparently I don't have write permissions on /system
it is unusable because android is annoying me with "service provider update.... the phone needs to be restarted." you can't click away either. over and over again.
SM-A236B

So i unlocked the bootloader and flashed with odin magisk patched boot.img and everything is working fine. Except SELinux, which is in permissive mode now. Jeez.

Question Is it possible to lock or relock it after unlocking the bootloader?

Does anyone know, I still have a STOCK system, without unlocked bootloader (and without root).
I uploaded the boot files extracted from "payload.bin" (init_boot, boot, vendor_boot) to it and patched it in Magisk.
In theory, Magisk reported no bugs during patching.
And here's the key question: is it safe to try to boot (not flash) OP11?
Of course, after unlocking the bootloader.
If after booting without flash it turns out that some functions do not work (screen brightness, changing colors, PIN locks, etc.), just restart OP11 and everything should return to the state before "boot".
Is it possible to lock or relock the bootloader later so that banking applications, contactless payments, etc. work?
regards
f.

qriozum said:
Does anyone know, I still have a STOCK system, without unlocked bootloader (and without root).
I uploaded the boot files extracted from "payload.bin" (init_boot, boot, vendor_boot) to it and patched it in Magisk.
In theory, Magisk reported no bugs during patching.
And here's the key question: is it safe to try to boot (not flash) OP11?
Of course, after unlocking the bootloader.
If after booting without flash it turns out that some functions do not work (screen brightness, changing colors, PIN locks, etc.), just restart OP11 and everything should return to the state before "boot".
Is it possible to lock or relock the bootloader later so that banking applications, contactless payments, etc. work?
regards
f.
Click to expand...
Click to collapse
I don’t have an answer to your question, but thought I would share that I got my OP11 yesterday. I updated to the latest ÔTA version, A.07. I then unlocked the bootloader and rebooted without issue. I am now looking to root, but not sure exactly how to get the files you mentioned. Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.

azsl1326 said:
I don’t have an answer to your question, but thought I would share that I got my OP11 yesterday. I updated to the latest ÔTA version, A.07. I then unlocked the bootloader and rebooted without issue. I am now looking to root, but not sure exactly how to get the files you mentioned. Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.
Click to expand...
Click to collapse
It is unbelievable that you have unlocked a bootloader and you have no problem with the pin/impression/blockade.
Here, two users say that they have a problem: https://forum.xda-developers.com/t/screen-lock-setup-crashing-unlocked-bootloader-rooted.4554073/
What is your OP11 version you unlocked?

azsl1326 said:
Can you share how you got those? I do have the payload.bin from the update. Thanks, in advance.
Click to expand...
Click to collapse
I used dumper to unpack "payload.bin":
Releases · ssut/payload-dumper-go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
After starting it, "payload.bin" will unpack the commands and you will have system partition images in the subdirectory.
Here two methods of obtaining root on OP11
Root OnePlus 11 via Magisk Patched Init_Boot/Boot
In this comprehensive guide, we will show you the detailed steps to root your OnePlus 11 via Magisk patched boot.img.
www.droidwin.com

qriozum said:
It is unbelievable that you have unlocked a bootloader and you have no problem with the pin/impression/blockade.
Here, two users say that they have a problem: https://forum.xda-developers.com/t/screen-lock-setup-crashing-unlocked-bootloader-rooted.4554073/
What is your OP11 version you unlocked?
Click to expand...
Click to collapse
I did see that but have had zero issues. Here's the version I am running.

qriozum said:
I used dumper to unpack "payload.bin":
Releases · ssut/payload-dumper-go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
After starting it, "payload.bin" will unpack the commands and you will have system partition images in the subdirectory.
Here two methods of obtaining root on OP11
Root OnePlus 11 via Magisk Patched Init_Boot/Boot
In this comprehensive guide, we will show you the detailed steps to root your OnePlus 11 via Magisk patched boot.img.
www.droidwin.com
Click to expand...
Click to collapse
Thank you!!! Did you unpack the payload.bin file on your android device or on a computer?

azsl1326 said:
Thank you!!! Did you unpack the payload.bin file on your android device or on a computer?
Click to expand...
Click to collapse
Unpacked on the computer.
Your model is 2451, i.e. the American version.
If I associate it well, then for your model there is only an incremental OTA, there is no fullOTA.
But I can be wrong.

I just got my American version through Amazon and I'm confused do we patch boot.img or init_boot.img now for root. And as for Amazon they ended up screwing people with the presale I payed 799.99 with a 100 dollar gift card today it lists for 699.99 so they essentially forced people to buy a gift card they didn't need even on checkout they were both itemized separate. I did manage to get them to refund the extra 100 though which was fine but I didn't like being cheated. The funniest part was when Amazon asked me instead of refunding me to my card if I wanted a gift card instead

scottlam1 said:
I just got my American version through Amazon and I'm confused do we patch boot.img or init_boot.img now for root. And as for Amazon they ended up screwing people with the presale I payed 799.99 with a 100 dollar gift card today it lists for 699.99 so they essentially forced people to buy a gift card they didn't need even on checkout they were both itemized separate. I did manage to get them to refund the extra 100 though which was fine but I didn't like being cheated
Click to expand...
Click to collapse
Patch init_boot.img for root

CoinsClassic said:
Patch init_boot.img for root
Click to expand...
Click to collapse
So to test I can type fastboot boot init_boot.img

scottlam1 said:
So to test I can type fastboot boot init_boot.img
Click to expand...
Click to collapse
This is not working, init_boot.img cannot be booted directly. So you can just flash it using "fastboot flash init_boot your_init_boot.img".

@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!

Swap_File said:
@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!
Click to expand...
Click to collapse
init_boot.img · qssi-user-13-TP1A.220905.001-1673015136383-release-keys--US · Android Dumps / oneplus / op594dl1 · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
CPH2451

Swap_File said:
@scottlam1 I don't think a init_boot.img exists for CPH2451 yet. If you have one, I'd love to know!
Click to expand...
Click to collapse
It's still factory sealed I'm just reading and learning now being cautious because I don't have msm to save my ass anymore.

CoinsClassic said:
init_boot.img · qssi-user-13-TP1A.220905.001-1673015136383-release-keys--US · Android Dumps / oneplus / op594dl1 · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
CPH2451
Click to expand...
Click to collapse
This prob isn't answered yet but if we patch init boot how would ota survival work on magisk because it patches boot img in other slot. Is that something the magisk dev might have to implement in the future. I know the dev works for Google but they still let him keep the magisk project

scottlam1 said:
This prob isn't answered yet but if we patch init boot how would ota survival work on magisk because it patches boot img in other slot. Is that something the magisk dev might have to implement in the future. I know the dev works for Google but they still let him keep the magisk project
Click to expand...
Click to collapse
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.

CoinsClassic said:
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.
Click to expand...
Click to collapse
Ok I use the public magisk on my 8t never played around with the canary builds

CoinsClassic said:
Yes, I rooted with A.06 (mine is CPH2449), and updated via Settings (200MB incremental OTA to A.07), patched into inactive slot, and voila, it kept root. Was using latest Stock Magisk Canary btw.
Click to expand...
Click to collapse
Friend, you really unlocked the European model, then you root and you have a screen lock/pin/fingerprint?
Automatic screen brightness?
Changing color mode also works?
I inquire, because as a colleague above I try to be careful, I don't have enough money to buy another copy.
In the neighboring thread of two users, he claims that the European version (2449) after the very unlocking of the bootloader allows them to set the PIN/screen lock - so no banking applications will work :/

qriozum said:
Friend, you really unlocked the European model, then you root and you have a screen lock/pin/fingerprint?
Automatic screen brightness?
Changing color mode also works?
I inquire, because as a colleague above I try to be careful, I don't have enough money to buy another copy.
In the neighboring thread of two users, he claims that the European version (2449) after the very unlocking of the bootloader allows them to set the PIN/screen lock - so no banking applications will work :/
Click to expand...
Click to collapse
I am the owner of this thread It's true, I cannot set any lock screen password/pin/fingerprint, etc.
I may need to try relocking and unlocking bl few more times, according to some users that should do the trick.

CoinsClassic said:
I am the owner of this thread It's true, I cannot set any lock screen password/pin/fingerprint, etc.
I may need to try relocking and unlocking bl few more times, according to some users that should do the trick.
Click to expand...
Click to collapse
Got an odd question does your camera glass have almost like a particle affect to it around the camera lenses but not on the lenses that's clear I hope I didn't get a defective phone would be a pain in ass to have to return