oh good call, i thumbs up this, i've also run into flash issues over USB3 on other devices.Are you using USB3 ports? I've had endless trouble trying to flash devices over USB3.
Strongly reccomend buying a small USB2 hub and trying via that.
oh good call, i thumbs up this, i've also run into flash issues over USB3 on other devices.Are you using USB3 ports? I've had endless trouble trying to flash devices over USB3.
Strongly reccomend buying a small USB2 hub and trying via that.
The USB3 ports on my laptop seemed to only work the second time a command is sent, and this doesnt work well at all for partitions.oh good call, i thumbs up this, i've also run into flash issues over USB3 on other devices.
Lenovo/Moto's LSMA tool is legit, but another place to download full official firmware zips (especially for those who use Linux only and don't have Windoze) is here: https://mirrors.lolinet.com/firmware/moto/lake/official/Thank you Andreas. I was already on this site: https://motostockrom.com/motorola-moto-g7-plus-xt1965-3 But it didn't look official and there had been too many downloads for the 10 rom hostet on Google drive already
EDIT: Worked with https://support.lenovo.com/id/en/solutions/ht102605! I'm on Android 10 stock QPWS30.61-21-3 now. First rescue however failed. Running it again from fastboot did the job.
Are you referring to 3 finger screenshot gesture?Very good job bro :good:
I would like to implement a gesture to capture the screen and have the option to use the gestures of android 10 in full screen.
If you want to keep TWRP installed after updating via OTA, use the "TWRP A/B Retention Script" Magisk module. You can find it's instructions for use in the modules description.I've just installed the rom with Open GApps and Magisk on a fresh and new device and I'm very happy. Very good work @Jleeblanch! After the installation I updated (to lineage-17.1-20200423-nightly-lake-signed.zip) using the built-in updater. Magisk was kept, however TWRP had been overwritten. Though that is not a problem for me.
Unfortunately I'm not able to reproduce this issue, but I'd really like to get to the bottom of it as pretty much every other Lake user on the Lineage IRC channel is complaining about it.That sounds really awesome that you found a way...
I am still suffering with WebView/Jelly & OTA.
In recent versions I suffered from issues that there was no reboot in the new slot and I did not know whether it was me or a kind of bug...
Are you trying to fastboot boot lineage-recovery.img? Cuz that's what it sounds like [emoji848]. Lineage recovery won't boot in that manner (whereas TWRP does) and needs to be flashed to the boot partition in order to be used for the first time. Afterwards you can simply reboot to recovery and it'll boot into Lineage RecoveryMore trouble with the lineage-17.1-20200424-recovery-lake.img file as well, did not want to boot at all, would just load up into the stock ROM (which I had to reflash after messing up the partition formatting) and the touch screen wont work until another reboot.
I got TWRP to boot though and managed to flash todays build.
Noticed something strange though, there's an app called "Prip" preinstalled? I looked it up and seems to be some carriers chat app, is this a mistake?
In regards to the moto cam, it says it's accessing the microphone, but I'm assuming the wrong one as there are 3 on the device, and other apps don't seem to have an issue.
It was working fine in the 16.0 build, perhaps the audio source mappings have changed around since?
Try using a different USB port on your PC?after flashing lineage recovery img, rebooting into recovery mode and sideload copy-partitions.zip i'm getting:
error: protocol fault (no status)
what should I do to proceed?
Try killing the ADB process and see whether it's running under admin or user account. Highly reccomend a USB2 port or hub as well.after flashing lineage recovery img, rebooting into recovery mode and sideload copy-partitions.zip i'm getting:
error: protocol fault (no status)
what should I do to proceed?
I did not restore with google. I restored with Titanium Backup. I had no problems adding Google Accounts or with WebView.Did you have problems with restoring the phone from google, adding the google account or with webview?
Such problems were really severe with first builds...
The same thing happened to me, it keeps loading on the logo, then it goes back to the recovery.Latest update from 27.04.2020 is a problem for my Moto.
Phone boot only in revovery.
I'm back to LOS26.04.2020.
Iirc it's in Developer settings.I recently found just by ocasion that there seems to be no option for disanling/enabling the update of the recovery image as implemented by this change link. Where should this option be found? Might there be a bug?
Latest update from 27.04.2020 is a problem for my Moto.
Phone boot only in revovery.
I'm back to LOS26.04.2020.
Ignore the 20200427 build. It may get pulled, it may not but there was some permission updates on Snap Camera which consisted of a few commits and we managed to only get the first one [emoji28]. The reason it's not booting is due to priv-app permissions for Snap. Next build will be fine and should also include the Webview fix as well [emoji106]The same thing happened to me, it keeps loading on the logo, then it goes back to the recovery.
That's where I looked, but it's not there.... Iirc it's in Developer settings. ...
to boot againfastboot getvar max-sparse-size &&
fastboot flash partition gpt.bin &&
fastboot reboot
I can't find it either.That's where I looked, but it's not there.
Can you tell me between which menu items it should be found in the Developer Options? In the upper most section there is no such menu item...
Then I would look and send a screenshot of that section.
Since the build containing that commit it has never shown up there...
I just want to know if its me or maybe a kind of bug...
That has always been a mess, afaik. My wife used a Honor 5X a while ago. Took me hours getting it to work. My mum has a Galaxy S5 where it is crappy as well. By a phone with enough internal storage.PS: Format my SD Card as internal partition is generally not working with Lineage, right?
Turn off voice match in Google Assistant, it has never worked with custom ROMs and is interfering with audio recording in every other app.Anyone else having problem with the audio filmning videos? It works with stock camera app, bit not when filmning with Instagram or Snapchat.