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
Related
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha
simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.
LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app
simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.
I upgraded from 5.1.1 to 6.0 by flashing the factory image without flashing userdata. Everything worked perfectly, but, as many people have noted, I get a "Your device is corrupt" message briefly on startup, before having the opportunity to enter my encryption code. Again, the phone functions just fine despite this.
I'm wondering what it is about my phone that causes this message to display. My bootloader is unlocked, though I don't think this alone should be a problem. I am completely stock, unrooted (though I was rooted on previous versions). As such, I don't think it can be a problem with the system or boot partitions, since, again, I have flashed and re-flashed these directly from the factory image. I don't see how it can be problem with userdata, since this isn't even decrypted when I get the "corrupt" message (i.e., I haven't entered the encryption code yet). Perhaps it's some problem with how userdata is encrypted?
Any logs that might give insight into where the fault is occurring?
Verity is the cause. That post should answer your question.
cupfulloflol said:
Verity is the cause. That post should answer your question.
Click to expand...
Click to collapse
Thanks for the link. I'm still not sure this explains my situation. I get a red "corrupt" warning telling me my device is actually corrupt, which should mean that system files have been modified. However, my system is unmodified; I know this because I have flashed it directly (multiple times).
Although it is extremely unlikely and might be a unique situation, Verity might have actually worked for what it was designed for, for once, and your system might actually be corrupted by either persistent malware or bad memory.
I would warranty return the phone, if possible.
Sent from my VS985 4G using Tapatalk
Wipe data factory reset from stock recovery.
trent999 said:
Although it is extremely unlikely and might be a unique situation, Verity might have actually worked for what it was designed for, for once, and your system might actually be corrupted by either persistent malware or bad memory.
I would warranty return the phone, if possible.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
droidstyle said:
Wipe data factory reset from stock recovery.
Click to expand...
Click to collapse
Thanks. I'm not looking really looking for a radical solution (wiping phone, returning it); I'm looking for an explanation (which might guide me to a less radical solution). Again, I wonder whether Verity makes a log somewhere. As I mentioned, my phone is working perfectly.
Hard to imagine it's persistent malware, since I've flashed every partition other than userdata (which is still encrypted when I get the "corrupt" message). Moreover, I'm by no means the first person to report this behavior.
NYZack said:
Thanks. I'm not looking really looking for a radical solution (wiping phone, returning it); I'm looking for an explanation (which might guide me to a less radical solution). Again, I wonder whether Verity makes a log somewhere. As I mentioned, my phone is working perfectly.
Hard to imagine it's persistent malware, since I've flashed every partition other than userdata (which is still encrypted when I get the "corrupt" message). Moreover, I'm by no means the first person to report this behavior.
Click to expand...
Click to collapse
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I didn't notice mine until I installed a custom recovery. Hrm..maybe I just didn't pay attention lol
Tower1972 said:
I didn't notice mine until I installed a custom recovery. Hrm..maybe I just didn't pay attention lol
Click to expand...
Click to collapse
i didnt get it either. but i flashed a custom kernel as well, which gets rid of that message.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I'm unlocked, stock and get no such message(s). Expecting it when I install a recovery though
Larzzzz82 said:
I'm unlocked, stock and get no such message(s). Expecting it when I install a recovery though
Click to expand...
Click to collapse
So I can't figure out what the true story is. Some people say that it happens to everybody with an unlocked bootloader, but, according to what you say, this isn't the case. I am stock in every way - recovery, bootloader, boot image, system image - and yet I get this warning. It's not a big deal, but it eats at me and makes me wonder whether there really is something corrupt about some aspect of my system.
NYZack said:
So I can't figure out what the true story is. Some people say that it happens to everybody with an unlocked bootloader, but, according to what you say, this isn't the case. I am stock in every way - recovery, bootloader, boot image, system image - and yet I get this warning. It's not a big deal, but it eats at me and makes me wonder whether there really is something corrupt about some aspect of my system.
Click to expand...
Click to collapse
It has to be changes to recovery. I'm running stock 6.0 with an unlocked bootloader and root and I have no such message on startup. Rooted and unlocked through Wugfresh NexusTool and temporary modified recovery option (non-persistent).
dasDestruktion said:
It has to be changes to recovery. I'm running stock 6.0 with an unlocked bootloader and root and I have no such message on startup. Rooted and unlocked through Wugfresh NexusTool and temporary modified recovery option (non-persistent).
Click to expand...
Click to collapse
No, if you're rooted, it's a different story. The modified boot image installed when you root disables verity checking.
I got the message after rooting my phone with CFRoot. Have done that before, always worked. But now the phone stops working after that boot message, I have reinstalled the stock image.
simms22 said:
it will appear when you boot up on marshmallow, when you have an unlocked bootloader.
Click to expand...
Click to collapse
I can confirm that this is not true. I ultimately factory-reset my phone from Recovery (it was acting strangely in other ways - Contacts crashing, for instance). My bootloader remains unlocked, but I no longer get the "Corrupt" message on startup.
I'm unlocked on marshmallow also and have never had that message
Take a look at here, it was my experience and solution.
https://productforums.google.com/forum/m/#!topic/nexus/sTu8Bdc1GLA;context-place=topicsearchin/nexus/category$3Adevice-security
Sent from my Nexus 6 using XDA Free mobile app
Semseddin said:
Take a look at here, it was my experience and solution.
https://productforums.google.com/forum/m/#!topic/nexus/sTu8Bdc1GLA;context-place=topicsearchin/nexus/category$3Adevice-security
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
A simple factory reset in Recovery was all I needed. But I was hoping for a solution that didn't involve wiping my phone, ... and some insight into why so many of us are getting this message with stock systems.
NYZack said:
A simple factory reset in Recovery was all I needed. But I was hoping for a solution that didn't involve wiping my phone, ... and some insight into why so many of us are getting this message with stock systems.
Click to expand...
Click to collapse
Glad you could fix yours with a simple factory reset. Mine was in a much worse situation where i immediately got the corrupted message once i entered gmail account into phone. Google reps couldnt find the answer to the issue but advised me to downgrade to previous os and take OTA to marshmallow, that definitly fixed the issue for me.
Sent from my Nexus 6 using XDA Free mobile app
Device verification on Android and Nexus can be a bit of an interesting subject.
In theory, dm-verity on a Nexus will ONLY validate the system image, and nothing else.
This is the key description that Google made regarding verified boot;
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
The key takeaways from that are;
1) an enforcing secure boot chain will involve validating each of the bootloader/boot partitions from the previous level, up to and including the boot.img.
2) The boot image contains the linux kernel and the verity_key file.
3) The verity_key file is the public key used to validate the contents of the metadata partition, which stores the hash tree for the system partition and is used to validate the contents of the system partition *on the fly*.
4) When dm-verity detects a change, it causes an I/O error.
5) On Nexus devices, the validation of the boot partition can be disabled.
The part that is interesting, is figure 2.
The part where it verifies metadata signature files --> no, causes it to reboot in logging mode and gives you the big ugly warning page.
Note that an unlocked Nexus 6 does NOT implement the yellow or orange warning states in its default configuration - see the description of "Class A". I'm not entirely sure if they can be enabled or not, but I've heard chatter of something to the effect of fastboot oem verify, which might enable validation of the boot partition.
So what happens during a dm-verity?
Well, when init tries to mount the system partition using dm-verity, it fails signature check. When it fails signature check, it sets a boot flag that it failed signature check, and *reboots*. The bootloader picks up this boot flag, and loads the error. If dm-verity PASSES signature check, it just continued boot as normal -- no rebooting.
So the approach for getting rid of that error message is actually this; if you tell init not to apply dm-verity, then the signature check is never even applied, so it continues boot as normal.
What isn't clear, is how it could be even remotely possible for a corrupt boot or cache partition to trigger a bootloader error. The only thing I can imagine, is maybe there is some additional check that isn't documented, or a bug in the bootloader that gets triggered when some boot flag is set wrong.
Is there any way to re-lock the bootloader so that I can use Google Pay? I have tried but it now says that a different OS is installed on the device.
I am not sure what I am doing wrong. I also am having trouble flashing the ROM, getting the following error:
Code:
Sending 'modem__a' (97815 KB) OKAY [ 2.157s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.168s
If anyone can help that would be great.
So far you can't. All you can do is use Magisk to spoof the bootloader lock. It will fail SafetyNet CTS since there is no way to lock the bootloader in the traditional sense. Locking it via fastboot only disables flashing of stuff, it does not not fix the fact that the stock rom is stuck booting with verity set to log only.
I've been rooted with Magisk for over a month and no issues what so ever with Google play or any other feature of the phone. Moto Z3 Play 1929-4 on Verizon. As for Safety Check, it shows success. cTs profile: true & basic integrity: true
So why would you want to re-lock your bootloader?
I'm even using Lucky Patcher, which Google Play hates and reminds me every day but just like what I say to Verizon, it's not your decision or your phone so just supply the services I pay you for and keep your little fingers out of MY moto.
any idea how to install otas ?
i cannot update ...
Mental1 said:
I've been rooted with Magisk for over a month and no issues what so ever with Google play or any other feature of the phone. Moto Z3 Play 1929-4 on Verizon. As for Safety Check, it shows success. cTs profile: true & basic integrity: true
So why would you want to re-lock your bootloader?
I'm even using Lucky Patcher, which Google Play hates and reminds me every day but just like what I say to Verizon, it's not your decision or your phone so just supply the services I pay you for and keep your little fingers out of MY moto.
Click to expand...
Click to collapse
cubano2031 said:
i cannot update ...
Click to expand...
Click to collapse
Update what?
Magisk?
OTA?
Sorry....pretty much the OTA’s.I’ve been trying everything in oder to get the zip file from January pach.I try to unistall Magisk too but the OTA fail to install and on top of that yesterday My rooted Moto z3 play start to acting weird ,the firger print option just disappear amd after a restar is back again ....
Mental1 said:
Update what?
Magisk?
OTA?
Click to expand...
Click to collapse
cubano2031 said:
Sorry....pretty much the OTA’s.I’ve been trying everything in oder to get the zip file from January pach.I try to unistall Magisk too but the OTA fail to install and on top of that yesterday My rooted Moto z3 play start to acting weird ,the firger print option just disappear amd after a restar is back again ....
Click to expand...
Click to collapse
This is probably a stupid question but have you tried starting over with a factory reset? As long as the bootloader is unlocked you should have no issues reflashing original ROM. I hope this isn't something that will pop up on my Moto z3P. It's hard to troubleshoot a issue without actually knowing when or what caused your problems to start. Do you use a separate launcher, theme, or anything outside the box of Moto? Have you installed TWRP? Or F'd around with your system files? A small little change in anything throws off the comparison between the same model phones as in why one experiences a problem & other exact same models don't. As of now I don't use TWRP or Lineage but I have been through my file system with a very fine toothed comb. It's amazing how much wasted memory is just sitting there with so much crap that will never ever get used. Why they would need to store bin's & img's for 5 other cell carriers is stupid. Although for a selected few, to unpack and dive into ripping one apart is fun & entertaining.
Mental1 said:
This is probably a stupid question but have you tried starting over with a factory reset? As long as the bootloader is unlocked you should have no issues reflashing original ROM. I hope this isn't something that will pop up on my Moto z3P. It's hard to troubleshoot a issue without actually knowing when or what caused your problems to start. Do you use a separate launcher, theme, or anything outside the box of Moto? Have you installed TWRP? Or F'd around with your system files? A small little change in anything throws off the comparison between the same model phones as in why one experiences a problem & other exact same models don't. As of now I don't use TWRP or Lineage but I have been through my file system with a very fine toothed comb. It's amazing how much wasted memory is just sitting there with so much crap that will never ever get used. Why they would need to store bin's & img's for 5 other cell carriers is stupid. Although for a selected few, to unpack and dive into ripping one apart is fun & entertaining.
Click to expand...
Click to collapse
Here is a interesting list
cubano2031 said:
i cannot update ...
Click to expand...
Click to collapse
I am running on the same issue: unlocked bootloader and if i try to do android system update i am getting
system integrity compromised.
i contacted motorola and they refuse to provide me any kind of support or solution for this issue as i have the bootloader unlocked.
funny thing they even advise me against updating android as it could be dangerous !!
I am european, the phone was bought i europe, as also explained on carlo piana blog (can't provide link sorry )
I would really like to initiate a case on Motorola refusing to provide any kind of support and saying my warranty is void.
moto z3 play
driverdis said:
So far you can't. All you can do is use Magisk to spoof the bootloader lock. It will fail SafetyNet CTS since there is no way to lock the bootloader in the traditional sense. Locking it via fastboot only disables flashing of stuff, it does not not fix the fact that the stock rom is stuck booting with verity set to log only.
Click to expand...
Click to collapse
tenho um moto z3 play fiz um relock no bootloader e agora estou tentado desbloquear o bootloader e nao consigor alguem ajuda aee :rolar os olhos:
I also am in the same boat. Let me explain the whole thing:
Device almost brand new RETUS 1929-4. Was with Oreo outta the box and get a couple of OTA updates. Then I tried to get the Pie update with the Lenovo App and couldn't got it. No matter what. At that point my bootloader was locked and I thought it was because of that. I unlocked my bootloader and I use the Lenovo App and now I am stuck in boot with veryty disabled message. In fastboot I try to update to pie and I also have the same. Only work with 8.1 and nothing but that. OTA pop up also is bugging me that I have an update but I can't update. What can I do?
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:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
ChronosTrigger said:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
Click to expand...
Click to collapse
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Confused still
CurtisMJ said:
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Click to expand...
Click to collapse
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
ChronosTrigger said:
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
Click to expand...
Click to collapse
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
WARNING: This file is really intended for a developer to use in making a rooted slot. Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? Although, mostly likely, it won't flash at all if you are rooted.
I used adb to capture the Razer Phone 2 MR2 OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
ChronosTrigger said:
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
Click to expand...
Click to collapse
Not quite... The update will likely fail to apply due to checksum failures. If it did go through it would probably brick the kernel so that's a good thing. Sorry, there's not really a way to automatically root after official OTAs as they update block by block between two known states, and neither is rooted. It's just sort of not possible, by design. You have to unroot, update and root again.
The OTA package translucentfocus has provided allows us to reproduce a single slot before the week's wait for the factory image so we can root sooner.
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
which OTA is this? Also how to update
xterminater07 said:
which OTA is this? Also how to update
Click to expand...
Click to collapse
Sorry, I didn't specify. It's the MR2 update for the Razer Phone 2. Original reply has been also updated with version information in bold.
How to update? Actually, I posted the OTA because it's really for someone to make a slot with root before Razer releases the Factory MR2 Images--as @CurtisMJ mentioned previously.
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Univsoldur said:
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Click to expand...
Click to collapse
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
CurtisMJ said:
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
Click to expand...
Click to collapse
Thanks for the detailed response I managed to get up with the previous owner on swappa last night. He told me he unlocked the phone but never actually got around to rooting it. He also said it is running stock and the reason magisk is still on the phone after a wipe is because magisk persists after a wipe.
Messages from him.
Sorry about that, I did unlock the bootloader but I never actually got around to rooting. I usually relock the bootloader before I sell it but I completely forgot. You can apply an ota because I never installed a custom recovery, something else I didn't get around to doing. You can easily relock the bootloader using adb. If you need help with this let me know and I can walk you through it. But the bootloader being unlocked has zero effect on ota's. You are all good to go as far as that goes.
Oh no you're absolutely fine with an ota. I just looked it up and you're absolutely right, magisk does survive a reboot now. Since I didn't load a custom recovery though an ota will install just fine. Although when an ota does install though it will most likely remove magisk because it will write over the boot.img with the factory one. Here is the link to the factory images. It includes instructions on how to install it. But honestly a new ota should be released any time now since the last one I think was November. Once that installs you will be completely back to stock.
Does this sound accurate to y'all. Thanks again
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
CurtisMJ said:
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
Click to expand...
Click to collapse
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
Yes, that will return it to stock and remove Magisk. No, if you flash the factory image you don't need to do anything further with the kernel.
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
DrGonzo6o said:
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Click to expand...
Click to collapse
The bootloader needs to be unlocked, yes. I had the unlocked one from the start, so I can't comment on how well that will work though.
Has anyone with an AT&T version successfully flashed unlocked firmware?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
I did post a full unroot guide...