Recent content by bornheim2

Me ... and?

mirrors.lolinet.com offers firmware for the Moto G8 Plus. I have a XT2019-1 on reteu. Did anyone try this with XT2019-1_DOHA_RETEU_9.0_PPI29.65-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip ? My phone says it is on PPIS29.65-24-2. What does the missing S in PPI29.65-51 mean?

Thanks, installing Gapps solved most problems. Some apps still made trouble but I could solve that by uninstalling and reinstalling them through the Play Store. I had to download the Magisk manager app from APKmirror. Installing the ZIP through TWRP again didn't help.

Problems with apps after updating to 16.0 I updated all my apps to the latest version available from the Play Store. Then I did the repartioning and updated from lineage-14.1-20171019-UNOFFICIAL-manta to lineage-16.0-20181020-UNOFFICIAL-manta. Before rebooting I installed Magisk 17.3. Now lots...

My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following: - Magisk Manager > Uninstall > Restore Images - Settings > System > System Update The phone started to download the OTA (about 300...

Most guides here are about rooting with SuperSU. Last month I decided to go with Magisk instead, since development of SuperSU came to an end. I did a complete wipe, installed Stock (8.1.0, patch level June 2018) and Magisk, then restored my Apps with Titanium Backup. Happy ever after. Now the...

Yeah ... well: that is what everybody is writing. But nobody posts a firmware and a command sequence leading to a working "mfastboot oem lock".

That would mean that no bootloader could be re-locked ever. Apparently at least the LG G5 can be re-locked.

Same error as all the other "working relock" threads: R:\>mfastboot flash boot boot.img target max-sparse-size: 256MB sending 'boot' (16384 KB)... OKAY [ 0.377s] writing 'boot'... (bootloader) Image signed with key bad key

Well, actually I do have a clue. You might want to try to read comment #17 in this thread. Where the clue is. Which I gave. Exactly one comment before yours. Cheers.

Actually: did Google forget your PIN? As far as I am concerned: Google still knows your PIN. It's you that doesn't.

[Solved] Can't start TWRP any more Solved, see here: https://forum.xda-developers.com/showpost.php?p=73361170&postcount=426 and the following posts.

That worked. Additionally: no need to download fwtool: there already is /system/bin/fwtool in the image. Indeed my dev_boot_fastboot_full_cap was 0. I set it back to 1, now I can boot directly to TWRP or flash it to recovery. Thank you!

I'm sorry I did not mention that: I'm on fastboot version 3db08f2c6889-android, the one you linked to. My bootloader is bootloader-dragon-google_smaug.7900.50.0.img. At least I think I'm on that, it's the same the July patch came with. The message "image verification failed" seems to indicate...

I'm on 7.1.2 (patch level July 2017, N2G48B). I would like to boot TWRP to make a backup before updating to the August patch. The device is unlocked. Fastboot fails to boot or flash TWRP: fastboot flashing unlock FAILED (remote: Device already unlocked) fastboot boot twrp-3.1.1-0-dragon.img...