Database Develop

I come to the conclusion...........

that not only devs given up with the g6 play, so have Motorola.
I have tried every way possible to re-lock and completely without an error, flash a stock firmware
i have had problems with boot.img recovery.img with every firmware, all saying bad key
i cannot in any way relock the bootloader.
every time saying please flash a valid android image.
I have tried every firmware image for my model xt1922-2
I have used search here, on many other sites, to no avail......
i can root quite easily, i have used guides galore, but nothing flashes correct
i am not a noob and have been flashing firmware since xdas early days...
help!

biggary said:
that not only devs given up with the g6 play, so have Motorola.
Click to expand...
Click to collapse
Given up? Since when did you see any one actively developing roms or anything for the G6 Play?
i am not a noob and have been flashing firmware since xdas early days...
help!
Click to expand...
Click to collapse
Then you know not to make multiple threads on the same issue? I am familiar with your issue but I don't have an answer. No one else does either it seems.
Sent from my moto g(6) plus using Tapatalk

biggary said:
that not only devs given up with the g6 play, so have Motorola.
I have tried every way possible to re-lock and completely without an error, flash a stock firmware
i have had problems with boot.img recovery.img with every firmware, all saying bad key
i cannot in any way relock the bootloader.
every time saying please flash a valid android image.
I have tried every firmware image for my model xt1922-2
I have used search here, on many other sites, to no avail......
i can root quite easily, i have used guides galore, but nothing flashes correct
i am not a noob and have been flashing firmware since xdas early days...
help!
Click to expand...
Click to collapse
It's very obvious, even for someone who has never flashed a single phone before, not to mess with the g6 play - you're stuck with whatever you've got. Maybe in the future that will change, but I find it unlikely.

At least you have an official version of TWRP. The G6 doesn't.

Ginger Bier said:
At least you have an official version of TWRP. The G6 doesn't.
Click to expand...
Click to collapse
Official and unofficial is not even important. For the G6+ we just got Official TWRP but if you flash anything with official twrp your device is soft bricked. However, unofficial build works great with the exception of 1 or 2 GSIs. Official was made by a dev who didn't test it(or have someone with the device since he doesn't own it) on our device and attached one of our devs name to it without him even knowing about it. For some reason Twrp team decided to approve it as official with out confirmation it even worked which is bad news imo and really disappointed me.
Sent from my Moto G6 Plus using Tapatalk

Mensagem no boot "verity mode is set to logging"

Hello everyone,
Every time my moto x4 is restarted, a message appears on the boot screen:
"verity mode is set to logging"
It is something quick, written in yellow and soon the device finishes the initialization.
I wonder if this affects anything on the device?
I make the following observations:
My moto x4 was in the version PAYTON_OPW29.69-26_SUBSIDY-DEFAULT_REGULATORY-DEFAULT_CFC.XML. As I was having problems with Wi-Fi on the device, I decided to unlock the bootloader and flash another version of the android. Finally I opted for PAYTON_FI_OPWS28.46-21-12_SUBSIDY-DEFAULT_REGULATORY-DEFAULT_CFC.XML, this after having tested other versions, all with success. But since I unlocked the bootloader and did the first downgrade this message appears at the boot of the device.
My moto x4 is an XT1900-6.
Another thing done through a previous search was to run the command "getprop ro.boot.veritymode" in the terminal, directly on the device, which returned: "enforcing".
Anyway, I'm not sure if everything is OK with the device or if I lost any important function. If it is a normal error and if it is not, I would like to know the solution to this problem.

This is "normal". I think you can ignore it. If you were worried about security and privacy, you would want it to be enforcing so that the phone wouldn't boot if it was modified. Most users do not want this since it would break a lot of things.
Edit: are you using any third party zips to hide root or pass safety net? They might mask the verity mode, maybe? I don't use them so I couldn't tell you the expected behavior.

gee one said:
This is "normal". I think you can ignore it. If you were worried about security and privacy, you would want it to be enforcing so that the phone wouldn't boot if it was modified. Most users do not want this since it would break a lot of things.
Edit: are you using any third party zips to hide root or pass safety net? They might mask the verity mode, maybe? I don't use them so I couldn't tell you the expected behavior.
Click to expand...
Click to collapse
I did another clean install, using the same firmware as android 8.1 (one), now I'm not using root, as I see no need. I hope there is no problem with this message on the boot screen. I hope I still receive updates via OTA.

To remove this message needs to flash the bootloader from phone variant. This file fix for XT1900-6.

filipepferraz said:
To remove this message needs to flash the bootloader from phone variant. This file fix for XT1900-6.
Click to expand...
Click to collapse
nice bro, it worked for me. :good: :fingers-crossed:

"verity mode set to disabled"

I unlocked the bootloader of my G7plus, installed TWRP and then used TWRP to install Magisk.
So far, everything is working, root hiding is working as it should and Magisk's "SafetyNet Check" is reporting success.
Yay.
Almost.
a) During the boot I'm getting a message in the top left corner saying "verity mode is set to disabled"
b) Google Pay won't work, probably due to a)
Questions:
1) Is b) really due to a), and if so
2) How do I get rid of a)?

hildeb said:
I unlocked the bootloader of my G7plus, installed TWRP and then used TWRP to install Magisk.
So far, everything is working, root hiding is working as it should and Magisk's "SafetyNet Check" is reporting success.
Yay.
Almost.
a) During the boot I'm getting a message in the top left corner saying "verity mode is set to disabled"
b) Google Pay won't work, probably due to a)
Questions:
1) Is b) really due to a), and if so
2) How do I get rid of a)?
Click to expand...
Click to collapse
1) no idea
2) that worked for me so far to use google pay (I just followed the instruction in #1, though there is a huge discussion and also some tools/scripts available within the discussion)

Hello, I have the same exact issue, plus the AR stickers in the stock camera aren't working anymore, and I suspect it's not a coincidence.
Any update on this would be more than welcome.
Alternatively, as I'm not sure I am going to do anything really useful with root access, I'd love if someone could suggest an un-rooting method... just in case. (I know this might sound like a stupid question, but years have passed since my last rooted phone, and I'm at a loss with all these new things around lol)
Thanks to anyone answering

Max Morden said:
Hello, I have the same exact issue, plus the AR stickers in the stock camera aren't working anymore, and I suspect it's not a coincidence.
Any update on this would be more than welcome.
Alternatively, as I'm not sure I am going to do anything really useful with root access, I'd love if someone could suggest an un-rooting method... just in case. (I know this might sound like a stupid question, but years have passed since my last rooted phone, and I'm at a loss with all these new things around lol)
Thanks to anyone answering
Click to expand...
Click to collapse
It's funny that you mentioned AR stickers not working for you now. I unlocked my bootloader today, and lost the function of AR stickers and Google lens. And I haven't even rooted. I'm going to lock the bootloader back to see if it makes a difference.

fossiltkm said:
It's funny that you mentioned AR stickers not working for you now. I unlocked my bootloader today, and lost the function of AR stickers and Google lens. And I haven't even rooted. I'm going to lock the bootloader back to see if it makes a difference.
Click to expand...
Click to collapse
I have rooted and passed the Safetynet in Magisk and Lens is working good. I never bothered with AR stickers elsewhere but in Wizzards Unite game they seemed to work just fine too

Unlocked bootloader, rooted and permanently installed twrp last night and now receiving this message. Is it anything to worry about, as in will any basic functions be affected? Not sure, because I haven't had a chance to test everything yet. If nothing will be affected, how to simply remove the message?

edit nvm

rev79 said:
Unlocked bootloader, rooted and permanently installed twrp last night and now receiving this message. Is it anything to worry about, as in will any basic functions be affected? Not sure, because I haven't had a chance to test everything yet. If nothing will be affected, how to simply remove the message?
Click to expand...
Click to collapse
After rooting, Magisk is supposed to care about the verity mode. AFAIK usually no app will know about the disabled state . Trying to hide the message may cause more harm.

Ok, thanks. I was just wondering because I also have a Samsung tablet (completely different device, I know) rooted using Magisk and the verity message is not present on bootup there. Also, in the magisk settings, both preserve encryption and preserve dm-verity are unchecked while they are checked on the G7. Is that just because they require different setups? I did flash the available bootlogo from https://forum.xda-developers.com/g7-plus/themes/bootlogo-modded-bootlogo-unlocked-t3910421 and it removed the warning screen about the bootloader, but the verity message remains. I guess those are different things?

The bootlogo only hides the message by using the same color like the message for the background. In my opinion modifying the logo partition to virtually let the message disappear makes no sense. If you want to see what is happening, it makes things complicated. Also the logo partition is modified now, which was one reason for not being able to update OTA. On the G7+ the unlocked bootloader seems to be reason enough to prevent OTA updates against Motorola support FAQ saying otherwise, so this doesn't matter anymore, but I still don't like it.

tag68 said:
On the G7+ the unlocked bootloader seems to be reason enough to prevent OTA updates against Motorola support FAQ saying otherwise, so this doesn't matter anymore, but I still don't like it.
Click to expand...
Click to collapse
The Moto G7 series has fundamentally problems to receive OTA updates. But to install it your device must be on stock. Otherwise the update could hard brick it since Google uses block based updates.

WoKoschekk said:
But to install it your device must be on stock.
Click to expand...
Click to collapse
Unlocking bootloader is the method for me to make sure I can do Nandroid backup and access files which are otherwise protected by running twrp one time. Maybe that I could root for Titanium Backup. That is all.
When I tried it, my G7plus was stock. Not rooted, no twrp.
As OTA did not run anyway, I rooted in the meantime. But using the Magisk manual for OTA updates, it should be possible to temporarily disabled Magisk - it still does not work.
I asked where to find the logfiles where you can see in which partition the error occurred (they are not where they used to be on older phones), but it seems no one knows the answer.

tag68 said:
When I tried it, my G7plus was stock. Not rooted, no twrp.
Click to expand...
Click to collapse
How did you try it? Did you receive the notification for a new update and then you pressed "install"?
tag68 said:
I asked where to find the logfiles where you can see in which partition the error occurred (they are not where they used to be on older phones), but it seems no one knows the answer.
Click to expand...
Click to collapse
The log would tell you that the compatibility check fails. The .zip runs a check of all partitions at the beginning which compares the verity hashes.
All logs will be cleared when you reboot the device. There is no log like a last_kmsg or something that gives you some information about errors before the reboot. To get logs like that you would need a Magisk module or a own script handled by Magisk.
The only way to run the update manually is to download the ota.zip, delete the compatibilty check inside the .zip and flash it through TWRP. But this could lead to a hard brick and is not recommended.

WoKoschekk said:
How did you try it? Did you receive the notification for a new update and then you pressed "install"?
Click to expand...
Click to collapse
I wanted to. But there was a message like (translated from German) "You are not eligible for system updates as system integrity is compromised." Install OTA was not available. So I could not update, against Motorola support FAQ OTA with unlocked bootloader.
WoKoschekk said:
The log would tell you that the compatibility check fails. The .zip runs a check of all partitions at the beginning which compares the verity hashes.
Click to expand...
Click to collapse
It is not the first device where I said 'only unlock bootloader to avoid that erase userspace, nothing else is being done for quite some time.' As mentioned I want to be able to root later, or do a backup starting twrp once, but not touching anything until I have a good reason to do so. The reason for root was that OTA did not work, then I said "then I can root and try topjohnwu method".
WoKoschekk said:
All logs will be cleared when you reboot the device.
Click to expand...
Click to collapse
That's why I did not boot normally, but instead started TWRP and searched for the logs. But didn't find them where they used to be.

Try to flash a clean ROM and boot it up. Then you will be able to download and install the OTA. Or as an alternative download the ROM on mirrors.lolinet.com
tag68 said:
That's why I did not boot normally, but instead started TWRP and searched for the logs. But didn't find them where they used to be.
Click to expand...
Click to collapse
Where did you look at? In /sys/fs/pstore?

WoKoschekk said:
Where did you look at? In /sys/fs/pstore?
Click to expand...
Click to collapse
The G7plus is my first a/b device. Before it was somewhere in /cache. Next time I'll try to look in /sys/fs/pstore, thanks for the hint.

tag68 said:
The G7plus is my first a/b device. Before it was somewhere in /cache. Next time I'll try to look in /sys/fs/pstore, thanks for the hint.
Click to expand...
Click to collapse
I asked because you won't find logs in this directory with a A/B device. It was only a usual path for non A/B devices. I just wanted to point it out to you.
Since A/B devices don't have a /cache partition (it's now /data/cache) the logs are stored in /persist/cache/recovery.

Anyone knows how to fix this issue?

What exactly do you mean?

Hola! si no me equivoco eso pasa cuando desbloqueas el bootloader y para entrar en modo fastboot o recovery, debes presionar los botones de subir y bajar volumen mas encendido

newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...

newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...
only modify a phone you are willing to throw away.......
##
pre-note: TWRP 3.3.1-0 -> fastboot boot twrp.img (this is temporary)
before doing anything, backup some little partitions: EFS, fsg, Vendor. Maybe others. You will need these to get back to a working stock.
##
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik ART cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
$$
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
newbie warning: don't re-lock bootloader, and beware flashing ANY custom ROM.
On the X4, the bootloader changes drastically between 8 and 9 as it introduces a dual file system which is used by OTA updates to alternate the live system, and as a backup if failure. It is not a true Treble system, only partial. You must not depend on being able to flash back and forth between O and P. If you update to P, stay there. I expect this to be exacerbated by those phones which update to 10, if that in fact happens(probably One/fi only). There is also much confusion as to which file system/setup any custom ROM uses, and thus, how you would get back to stock, if that is even possible. Be very careful and assure yourself that you are fully willing to lose permanently your new phone before you do anything. Please read posts in these forums.
I've seen many posts of folks, mostly noobs, who have flashed ANY custom ROM Lineage and are unable to get back to a working stock. Sounds super simple but apparently it's not. Best to assume that if you try things, especially Lineage, that you will never be able to get back to a working stock. Read a bunch of posts here and you will realize that.
I've also seen a bunch of folks on this phone, and other phones who have run a bat file to flash their phone which contains the line
"fastboot oem lock" or similar.
Don't do it!!! - This will lock your phone and you will never be able to do anything with it again. It is totally unnecessary to lock your phone. Folks who should know better are leaving bat files lying around with this command. If you use one of those bat files to flash your phone, just check and remove that command line. Else you will have destroyed your phone. That's one of those things that "sounds good" until you do it.
EDIT: You can run stock on a bootloader unlocked phone - I do it all the time - plays PoGo just fine. I don't know about banking apps - I don't use them as I assume any 10-year-old can and will hack my phone.
EDIT: 6Feb2020: folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
EDIT: this was successfully fixed. see: https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771 my guess is only works if you haven't changed bootloader or file system - NO custom ROM.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.

Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?

St.Noigel said:
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
Click to expand...
Click to collapse
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.

KrisM22 said:
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
Click to expand...
Click to collapse
OK. But I unbrick it. Now I have fully loaded system, but without WiFi ot mobile network.. It`s problem - I can`t turn on OEM unlocking.. (
Goшng to try to find solution
UPD. Everything work well now. But it my device I have custom stock flashed. Not sure it`ll work with LOS onboard

its to late for me

llue45 said:
its to late for me
Click to expand...
Click to collapse
Yeah, I know. You're one reason I posted this.

modified OP

change: from "Lineage" to "any custom ROM"

hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .

JavaShin said:
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
Click to expand...
Click to collapse
Good to not be trusting!!!! With this (or any) phone, I recommend you get only from a place (like ebay) where you can easily return it and get your money back. ebay can force a reluctant seller to refund your money. Assure that the seller has a 99% + rating and says they will accept returns and pay for return shipment, usually for 30 days. I don't think you can easily tell if it has been unlocked and re-locked - only that it works perfectly, or doesn't. You can check the ID of the ROM in your phone against the latest for your area by checking lolinet.
When you get it, check all functions and assure IMEI is present. check wifi, BT, etc etc. Make calls. Check that the phone works with the towers in your area and with a local SIM. etc etc. read here and find the things that folks having problems where it won't do things and assure your phone will do it. Install Pokemon Go on it and play it briefly to assure your phone hasn't been modified. I have no idea if any of these phone will work with any banking or payment apps, and each app will have it's own specific checks that it performs against the phone. Test what you will use. Fully. ASSUME NOTHING!!!
As far as rooting it and/or unlocking it, I would strongly advise against it. For this particular phone X4 I would determine that it works perfectly and then NOT modify it. Unless, of course, you are willing to throw your phone away and buy a new one without a second thought(most of us don't have that kind of money!). Mine happened to have been unlocked when I got it from ebay but it was on a stock 8.1 and it was able to, and did OTA update to the latest Pie stock ROM. Thus I was easily able to assure if was okay. It being unlocked seems to have affected nothing. I have never tried to root it or do anything to it (recovery or otherwise) as I read far too many posts of folks here who had rendered their phones incapable of returning to a working stock, and only on a limited custom. Not what I wanted. I have not heard of anyone successfully getting one of these phones back to a FULLY WORKING stock state.
The days of getting a phone and easily modifying it and then returning it to stock may be gone. Get a phone you will enjoy, and use it! Unmodified!!! Welcome to pre-Treble part1a . Expect a few years of growing pains.
I like my phone and enjoy not having to worry about whether a custom ROM will work and constantly be chasing updates and fixes. I use a case - I believe it is this one
https://www.ebay.com/itm/For-Motoro...hash=item33d89fee5a:m:mU5XV7jSj1TfD_kr-L4VT9g
which, so far, has protected it from several minor falls. I would never use any phone w/o a case!!!

But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .

added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.

OTA issues
KrisM22 said:
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
Click to expand...
Click to collapse
I posted a new thread on these OTA issues with the X4 at https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771. I was never presented with an "option" to install the latest OTA, it just automatically attempted to install (apparently a FORCED update) and is continuing to do so and failing ad infinitum. That phone works, just getting constant failure notifications. Question is, how to stop the attempted updates?
The second identical phone (updated per Magisk OTA tutorial instructions) is borked, with no phone connectivity. Can these be recovered by wiping/flashing stock rom PPWS29.60-39-6-2 and get them operating again as stock? I can forego the OTAs if there's a way to stop them from screwing up the device.
I never had other than stock recovery on either of these phones, I always boot TWRP via fastboot to do mods.

EDIT: XDA system is stalling and caused double post. Sorry. Mod please delete.
-deleted by me -

@redwoodie , please don't post to this thread. I read all your threads/posts but have no information.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
As to whether "x" strategy will work, you are certainly free to explore that on your own, in your own thread.
No one here knows. I am certainly not going to experiment on my own phone and run the likelihood of having to buy a new one. Folks like yourself keep showing up and doing just that because they are SURE it will work. But it hasn't.
Read all the posts.
There are very few folks left here on this forum. Once they have destroyed their phone, and tried a bunch of things, they move on.
THERE IS NO SOLUTION.
This thread is only to warn newbies.
I personally know nothing about the phone other than what has been posted by others.
Read it.
If you discover a true solution that allows a phone to work perfectly ON STOCK, please post it and you will make lots of folks happy, assuming it is repeatable.
However, no known solution.
But, again, you are free to explore solutions - just not in this thread, please. Thanks.

added paragraph at top:
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik-ART-cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!

This guy is full of crap
KrisM22 said:
only modify a phone you are willing to throw away.......
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Click to expand...
Click to collapse
I've literally put so many different custom ROMs on this phone. I've bricked it, unbricked, hard bricked it and soft bricked it. Stop misinforming people bro. The Moto G6 I would say to be careful with but still I wouldn't make a post like this guy. The Moto x4 just requires a little prep to make it a full treble, GSI accepting, custom Rom beast. Plus there are a few official ROMs out there even Android 10 for the Moto x4 specifically. Don't be scared. Just research a lot and follow instructions
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
JavaShin said:
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
Click to expand...
Click to collapse
The op is a cracker Jack

Ims status not registered
Guys i flashed custom rom without taking backups of efs and all,so i ended up with ims status not registered because of that my volte is broken mine is retin.I tried to flash stock firmware but the imei is broken.Any way to fix this?

bumpsi since apparently folks are not reading this. mod a phone, likely lose it. relock a phone and def lose it.

Op 3T not bricked, all working, stock ROM, yet I CAN'T re-lock bootloader in any way

Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks

Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?

pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks

The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip

pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened

MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!