In the german forum Android-hilfe.de it was written that Motorola stopped delivering OTA to unlocked devices with Android 9.0 Pie. Documentation would be somewhere on xda, but I didn't find it by now.
[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]
- Thread starter Jleeblanch
- Start date
Everyone gets that after bootloader is unlocked, you must realize that vendors need to make taking control of your device seem like the end of the world. Like most here I simply installed a different bootlogo (this message is simply on a bootlogo) available here in the forum to get rid of it:
https://forum.xda-developers.com/g7-plus/development/bootlogo-modded-bootlogo-unlocked-t3910421
Yes, I'm OK with all the warnings and stuff. I did accept the unlocking agreement after all. However just changing the boot logo that I see maybe once a week does not really help. If the updates exist and the system was not changed at all, why not allow them just because of unlocked bootloader. I'm sure some other ways of maintaining system integrity exist
(this is not to critisize you or anyone here but Lenovorola)
I installed Magisk yesterday, did Safetynet check and, surprise: a system update popped up. I click install and it starts to download and apply... and then: at 12% "there was a problem updating ..." and no changes made. bam.
and the update notification keeps pestering me again and again. I'll have to find a full system image with updates included
Maybe see this post rather than repeat myself:
https://forum.xda-developers.com/showpost.php?p=79655875&postcount=10
I heard since that post that relocking bootloader still won't get OTAs and still get system compromised message. Lenovorola stated that unlocking shouldn't affect receiving OTAs so they aren't living up to the information they provided to users. It appears that after unlocking G7 Plus we will need to upgrade manually either by flashing full firmware or if lucky TWRP installable zips made by a dev from captured OTAs.
Yes, I do plan on implementing decryption support.
I'm gonna need a little more to go on than that. Like what stock firmware are you on?
i'm on ppws29.98-66-2 april security update. i did root with magisk so that i could install viper4android.
Thanks for the tip. Well, it seems the only choices are to either flash full images with updates included from lolinet, or wait for someone to capture OTA's to make them flashable zips
Question
Do i have to unlock the bootloader for this and how can i do that
Do i have to unlock the bootloader for this and how can i do that
i was mistaken about twrp touch not working. when i typed in the string, i omitted the .img on the end. through trial and error, i finally went back and redid everything from the beginning, and flashed dirty the twrp . i am now rooted and relieved. forgive my mistake. everything seems to be working great xt1965-2
. .
. .
You do need to unlock your bootloader, yes. You can find instructions to unlock on Moto's website (linked below). Just note, that doing so will wipe all your data, including Internal Storage.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I have TWRP installed, and I have what is no doubt a really daft question..
But..
How do I boot into TWRP?
I have tried Power + Volume down - I get the bootloader with options:
Start
Restart Bootloader
Recovery Mode - Brings me to the 'no command' screen
Power Off
Factory Mode
BP Tools - Seems to reboot as normal
QCOM
Bootloader Logs
Switch Tools Mode - Does nothing
Barcodes
I can do it using cmd on pc, just wondering how to do it without PC.
But..
How do I boot into TWRP?
I have tried Power + Volume down - I get the bootloader with options:
Start
Restart Bootloader
Recovery Mode - Brings me to the 'no command' screen
Power Off
Factory Mode
BP Tools - Seems to reboot as normal
QCOM
Bootloader Logs
Switch Tools Mode - Does nothing
Barcodes
I can do it using cmd on pc, just wondering how to do it without PC.
Last edited:
Are you sure it is installed? Do you mean it was flashed, or do you mean it was booted?
Usually it is not recommended to flash TWRP. If you use "fastboot boot", it gets transferred once without flashing. So you need a PC every time you want to start it.
If you want to flash twrp, you need to boot twrp and then flash it. Explanations see here. When twrp is correctly flashed, you start recovery from that boot menu.
I flashed/permanently installed it using the guide from the OP, but can't boot into it from that menu.
I will wipe and start again, as I am having other issues, and was going to anyway.
Also my folders are garbled names, like in this
I will wipe and start again, as I am having other issues, and was going to anyway.
Also my folders are garbled names, like in this
Thanks for the help. I have wiped and started again, and can boot into it no problem now :victory:
As an FYI, the first post is not updated with the most recent twrp. I learned this the hard way when I encountered the touchless interface, and had to reboot and reinstall the latest version that's in post 17.
Update!
Changes:
- twrp 3.3.1
- decryption working (booted and installed)
- possibly fix touchscreen not working for everyone (need more confirmation)
- new installer zip for easier updating, and can be flash in Magisk Manager as a module
** Downloads **
• TWRP || twrp-3.3.1-v4.0-lake-jlb.img
• INSTALLER || twrp-installer-3.3.1-v4.0-lake-jlb.zip
Changes:
- twrp 3.3.1
- decryption working (booted and installed)
- possibly fix touchscreen not working for everyone (need more confirmation)
- new installer zip for easier updating, and can be flash in Magisk Manager as a module
** Downloads **
• TWRP || twrp-3.3.1-v4.0-lake-jlb.img
• INSTALLER || twrp-installer-3.3.1-v4.0-lake-jlb.zip
I've updated the OP with links to the new build and some new info regarding installation.
I'm waiting on some feedback to see how the new update is going for you guys before I apply for official status to make sure I haven't missed anything. As far as I know, everything should be working. I've added in decryption support and have verified it successfully decrypts data when fastboot booting twrp, as well as installing twrp permanently. I also rewrote the touchscreen module loading script to load the touchscreen modules directly from /vendor/lib/modules rather than having to ship them with the build and update them each firmware update. My hope is that this method works for everyone, regardless of the firmware version. I've received some confirmation on a few firmware version so far, but more is better [emoji6]
I'll upload some screenshots shortly too
I'm waiting on some feedback to see how the new update is going for you guys before I apply for official status to make sure I haven't missed anything. As far as I know, everything should be working. I've added in decryption support and have verified it successfully decrypts data when fastboot booting twrp, as well as installing twrp permanently. I also rewrote the touchscreen module loading script to load the touchscreen modules directly from /vendor/lib/modules rather than having to ship them with the build and update them each firmware update. My hope is that this method works for everyone, regardless of the firmware version. I've received some confirmation on a few firmware version so far, but more is better [emoji6]
I'll upload some screenshots shortly too
One pic is data successfully decrypted in twrp. The other is the twrp-installer in Magisk Manager 
Magisk supports OTA. I'd like to have that possibility (although I didn't have an update by now, so it is untested for me for A/B-device), therefore I usually only boot twrp via fastboot. Is it possible to install TWRP after Magisk and keep that workflow? If I understand correctly, Magisk restores its backup of the boot partition. But this would only be possible on the slot where Magisk is installed, right? Would it be possible to install TWRP only on slots where Magisk is installed and has a valid backup of the original boot partition?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone