Related
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?
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
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!
I rooted my device with magisk but I wanted to undo the root and return as it was before, I would like to know if there is any method to return the factory bootloader? I already locked the bootloader but at each restart it appears a message
"Your device has loaded a diferent operating system. Visit this link on another device. motorola.com/unlockbootloader" After this boot message the system starts normally, but I want a solution to remove this warning from the boot.
bilabongsurf said:
I rooted my device with magisk but I wanted to undo the root and return as it was before, I would like to know if there is any method to return the factory bootloader? I already locked the bootloader but at each restart it appears a message
"Your device has loaded a diferent operating system. Visit this link on another device. motorola.com/unlockbootloader" After this boot message the system starts normally, but I want a solution to remove this warning from the boot.
Click to expand...
Click to collapse
After unlocking, you can never remove that message ever again. You can only hide it by editing boot.img.
mrsiri said:
After unlocking, you can never remove that message ever again. You can only hide it by editing boot.img.
Click to expand...
Click to collapse
How i do this?
bilabongsurf said:
How i do this?
Click to expand...
Click to collapse
Custom Logo.bin(s) for all Moto G7- get rid of root warning screens hide "bad key"
Custom Logo.bin(s) for all Moto G7- get rid of root warning screens hide "bad key" Neither of these logo.bins are going to shorten the 5 second wait Motorala puts on a unlocked. Rooted phone. That is only going to happen with a custom ROM...
forum.xda-developers.com
I remember doing this to my own Logo.bin but I don't remember the name of the program. Anyway this should work fine as long as you pick the right model, which I'm assuming is G7 Plus. Do this at your own risk. What it basically does is put the logo motorola you see when you start phone the moment the warning shows up. This means it hides the warning, not get rid of it. It's a cosmetic solution.
I posted twice same stuff