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.
Related
Good morning droids,
I was looking around for info on the "phone storage encryption" option which requires a PIN when the phone is first powered on. This sounds nice conseridering the amount of information contained on our devices these days.
I think this is a stock HTC feature but I wasn't finding much in other forums. I'm currently running viper rom which has me wondering a few things:
Where in the boot process does it prompt for decrypt? Would you still be able to mount images from storage-- like does it prompt before the bootloader starts? would you still be able to use/nandroid/mount roms in a custom bootloader? Are there any recovery options? if it all goes to hell would I still beable to flash back to stock? Can encryption be undone after? My main concern has to do with when in the boot the storage is decrypted and how it affects the use/flashing of roms.
With all these questions I think the resounding common sense answer is "its just not worth the potential fallout." but I'll ask anyway...
Thoughts?
CarbolDroid said:
Good morning droids,
I was looking around for info on the "phone storage encryption" option which requires a PIN when the phone is first powered on. This sounds nice conseridering the amount of information contained on our devices these days.
I think this is a stock HTC feature but I wasn't finding much in other forums. I'm currently running viper rom which has me wondering a few things:
Where in the boot process does it prompt for decrypt? Would you still be able to mount images from storage-- like does it prompt before the bootloader starts? would you still be able to use/nandroid/mount roms in a custom bootloader? Are there any recovery options? if it all goes to hell would I still beable to flash back to stock? Can encryption be undone after? My main concern has to do with when in the boot the storage is decrypted and how it affects the use/flashing of roms.
With all these questions I think the resounding common sense answer is "its just not worth the potential fallout." but I'll ask anyway...
Thoughts?
Click to expand...
Click to collapse
I don't believe that recoveries are able to update a phone with an encrypted data partition unless you're using stock. I do believe you can flash back to stock if something goes wrong, although you would certainly have to format /data to get back into it. However, the actual login process (if I remember correctly, it's been a while) is that the bootloader starts you in a "dummy" environment of sorts that just asks you for your password. If it checks out, the system reboots, passing that key on to the "real" operating system which decrypts the data volume.
I'd echo though that it's really not something you should fool around with.
Couldn't find much about this varient just wanted to ask a few questions.
1. Do I treat it like every other google play nexus? Unlock boot loader, flash twrp, boot, backup, reboot, wipe, install ROM? No different partition weirdness?
2. Cm12, are the hotspot checks removed? Fiance is limited data plan I'm not so while out she normally uses my data via hotspot.
3. Cm12 have notification light activated and customizable?
Don't really care about the Sim lock honestly. Been with ATT forever and poor so not leaving the country anytime soon.
Thanks, sorry for repeat questions just didn't get solid answers from things I found.
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
squattingdonkey said:
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
Click to expand...
Click to collapse
At least you answered my bricking level question! Thanks!
CM 12 does have working hot spot on AT&T and customizable notification light. And, boot logo is easily removed after root.
Somehow I soft bricked my n6. I unlocked boot loader, installed twrp, went to backup and it couldn't find any partitions. Tried the flash all script from google factory image and that failed as well. Had to flash boot radio recovery etc images each manually to get back to a booting phone. Then installed twrp again and backup and flashing worked.
It was an adventure but I'm good now. Weird not sure why it did that. Must have been an encryption issue.
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
ajjames01 said:
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
Click to expand...
Click to collapse
Oops yeah that may have been it. I just did the usual fastboot OEM unlock code. Mild panic attack but when I saw I could get to the bootloader I knew I could save it.
After installing the latest Concept (3571), I unlocked my bl (which I'd locked previously), installed TWRP and then flashed the DRM-fix for Concept. My phone's working fine, but now when I power up I get a red warning with the wording: "Your device is corrupt. It can't be trusted and may not work properly."
How serious is this? Is this just the way that MM reacts to unlocked boot loaders, non-stock recovery or other such mods?
If it's just a warning message, I'm not worried, but I thought I'd check with you folks.
Thanks.
varxx said:
After installing the latest Concept (3571), I unlocked my bl (which I'd locked previously), installed TWRP and then flashed the DRM-fix for Concept. My phone's working fine, but now when I power up I get a red warning with the wording: "Your device is corrupt. It can't be trusted and may not work properly."
How serious is this? Is this just the way that MM reacts to unlocked boot loaders, non-stock recovery or other such mods?
If it's just a warning message, I'm not worried, but I thought I'd check with you folks.
Click to expand...
Click to collapse
Relocking the boot loader did not get rid of the message. For now, I'm going to live with it, as I'm hoping it's an inconsequential warning.
Unless someone knows better, I don't plan to remove TWRP or undo the DRM fix, one or both of which are probably what's prompting this message.
[Aside: Looks like I've become my own best friend. Now if I can get myself to pick myself up at the airport next week....]
I found this:
http://www.droid-life.com/2015/07/27/operating-system-warnings-may-soon-come-to-your-boot-screen/
which suggests that this is just a routine warning that tweakers should expect to encounter.
After I blew away my DRM keys because of ignoring this sort of warning, I've become a little more paranoid.
Still, I'd like to hear anyone's thought. Actually, I don't want to hear your thoughts. That sounds horrifying. I'd like to read your opinions on this matter.
Thanks.
varxx said:
I'd like to read your opinions on this matter.
Thanks.
Click to expand...
Click to collapse
I guess it's because TWRP has modified /system partition on it's first boot. Upon my first flashing of Concept rom (~2 months ago) and flashing TWRP along with SuperSU it did show that warning, but that's because I let TWRP modify /system partition rather than keeping it read-only.
Just yesterday I went on to flash Concept again (coming from 5.1.1 which was flashed through Flashtool as well) when I booted into recovery (flashed using fastboot) I denied TWRP's request to modify /system, and before flashing anything in recovery I have made sure that /system is read-only (In TWRP -> Mount), that was highlighted by Russel in Concept rom thread.
No warning for now, and I guess it won't show up anyway. I don't think you should worry about it though.
Cirra92 said:
I guess it's because TWRP has modified /system partition on it's first boot. Upon my first flashing of Concept rom (~2 months ago) and flashing TWRP along with SuperSU it did show that warning, but that's because I let TWRP modify /system partition rather than keeping it read-only.
Just yesterday I went on to flash Concept again (coming from 5.1.1 which was flashed through Flashtool as well) when I booted into recovery (flashed using fastboot) I denied TWRP's request to modify /system, and before flashing anything in recovery I have made sure that /system is read-only (In TWRP -> Mount), that was highlighted by Russel in Concept rom thread.
No warning for now, and I guess it won't show up anyway. I don't think you should worry about it though.
Click to expand...
Click to collapse
O.K., that makes sense. I guess MM has added security features, because I've been using TWRP off and on for a long time but have never seen this. I'm reassured that someone else feels it's not serious.
I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution
cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...
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