I'm updating to the latest available software for my Moto G5 Plus.
I've used the phone since 2018 with TWRP and LineageOS.
I've been more cautious about checking and verifying signatures lately.
I downloaded the TWRP App from the official TWRP site, with their public key, and the Apps' .ASC signature. Using Gpg in Windows to verify, the signature confirms authenticity.
I've not used the App in the past, and am more comfortable doing things manually, so I downloaded the latest version of the TWRP recovery along with it's ASC signature, and it *fails* it's signature check.
This was with version 3.5.2_9-0.
I tried other, earlier versions, which also failed:
3.5.1_9-0
3.5.0_9-0
3.4.0-0
3.3.1-0
3.3.0-0
3.2.3-1
3.2.2-0
3.2.1-0
and 3.1.1-0 all fail their PGP signature check against their accompanying ASC.
Anyone have any thoughts about this?
Additional info - This was from the TWRP website.
Related
Today, I tried to flash boeffla kernel and I got error "this package is for OnePlus2. This device is oneplus2"
I'm on official TWRP 3.0.0-1 and I downloaded directly from twrp.me
Yes, I did check md5 before flashing
See the screenshot in the attachment
You can see that people over here have the same problem as well
https://forums.oneplus.net/threads/...0-1-this-package-is-for.431689/#post-14553969
I've had the same problem with twrp 3.0.X Switch to 2.7.X and its fixed
For some bizarre reason, Wileyfox has been rejecting sending me latest fastboot and recovery images... Until today.
I really hope and expect more future collaboration between their technical support assets and us, starting by myself, to provide as much info and solutions as possible to you all, the community.
For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS163B.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader) - MD5
FASTBOOT IMAGE (2GB) (requires open bootloader) - MD5
INCREMENTAL UPDATE THREAD (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
They have also attached some documentation I left in the attachments, in case someone is interested or needs detailed instructions on how-to upgrade their devices.
Many thanks Ramvir for sending everything in!
Thank you, just updated my Swift 2X and flashed the recovery image in TWRP, then flashed magisk and it seems to be working well so far!
Yeah thanks linuxct for your work and contribution.
Because there is (not yet) a debloater for this version, is it than reguired to flash magisk or is superSU enough??
I think you can still use the most recent debloater, it worked for me. Magisk is still needed. I'm still on Magisk v12 and SuperSU 2.79 because I could not get other combinations to work.
Hello. cloud.mail.ru/public/JEWW/bMe4rXfbg/Wileyfox%20Swift%202%20series/Fastboot/
Cloud with official roms for marmite
eek:n reboot a notice pops up saying vendor image is a mismatch. So I downloaded the correct image file OPM 7.181205.001 and the radio and bootloader files to my phone. Now what do I do with the files? I am 74 and a non-techie guy. Help! Thanks!
You boot into the bootloader and install the updated bootloader and radio with fastboot. The updated vendor image can be installed with TWRP.
If you dont care about your data (or just backup it) you can redo everything:
1. Use the official latest google image for the nexus 6p to reinstall the whole os with the command "flash-all": https://developers.google.com/android/images#angler
2. Download official TWRP image (the part with the download links): https://twrp.me/huawei/huaweinexus6p.html and follow the "Fastboot Install Method (No Root Required):" part
3. Boot into the now installed twrp recovery and install the latest lineageos image
3.5(optional) install latest opengapps pico image form here https://opengapps.org/ to have the closed source google crap.
4. Done. You have now latest bootloader, latest radio, latest vendor, latest twrp and latest Lineageos.
Which TWRP do I use for Android 10 ROM´S? For me everything breaks off when installing with error 7.
Both the latest vers of official TWRP or Orangefox works. Error 7 usually indicates a corrupt .zip due to download issues. Normally a fresh download solves the problem. Perhaps try a different but stable Wi-Fi AP that's available to you.
For me its working latest twrp from official website.
Use the official twrp from site. No issue at all.
Ramdisk from Huawei official firmware is required in order to patch Magisk and acquire root privelages in Openkirin LineageOS builds. Can't apply patches to rom from TWRP because TWRP doesn't support custom rom decryption in this case.
Since other people may be running into a similar issue I figured I would write down my process and share it for the reference of others. I do not plan to support this thread, I just wanted to share what I did that worked for me to remove some of the legwork for research.
Disclaimer:
This isn't, by any means, a recommended method to achieve this end.
Essentially, I ran into the predicament that Huawei and alternative sneaky Russian sites for hosting the firmware files for Huawei Devices are down as of writing this.
Namely:
Online firmware database ⋆ TEAM MT Developers
< PREVIOUS FIND MODEL NEXT > Дата изменения Полное название Файлы обновления Размер Тип G g v f 2021.11.09 MED-LGRP2-OVS 10.1.0.195 filelist 0 OTA 1458 104 519745 3 2021.11.08 patch01 filelist 0 OTA 1458 104 525603 1 2021.11.08 TAS-LGRP1-CHN 11.0.0.170 filelist 0 OTA 1458 104 525098 1 2021.11.08...
pro-teammt.ru
So I could no longer use the site to download the official firmware for my Honor 7X and extract the ramdisk from it in order to patch Magisk to that ramdisk image.
Well, against the wishes of the openkirin project, I installed a modified version of TWRP customer recovery in order to manually dump the ramdisk image already present inside of the Huawei (which, in my mind, should have been the same one from the OEM that would have been extracted from an official Huawei update). The TWRP recovery version that I used came from the P10 Lite TWRP test build 0.5 from the thread I listed below. Hacky as all hell, but it worked for what I needed.
To get the ramdisk you need to go into TWRP and do backup --> ramdisk. It will drop it in your phone. Likely underneath /sdcard/TWRP.
Dump command to send to Linux(what I'm using, should be same on windows):
adb pull /sdcard/TWRP TWRP
The ramdisk dumped itself as a `.win` filetype, so I simply renamed the file extension to `.img` so that Magisk would recognize it and apply the appropriate patch.
With this dumped ramdisk image I added it to my phone and used Magisk to patch magisk to that dumped ramdisk, which I then transferred back to my computer.
I then booted the phone into bootloader mode:
adb reboot bootloader
and then flashed the newly modified Magisk ramdisk:
fastboot flash ramdisk magisk_patched-23000_9FXew.img
Upon rebooting my Huawei:
fastboot reboot
was able to verify with Magisk that I now had both TWRP custom recovery without issue and access to root privelages inside of LineageOS (which is good and ignores the need for TWRP to be able to decrypt custom rom contents)
Since TWRP cannot decrypt the contents of a custom rom in this case, being able to use TWRP to dump the ramdisk was an essential step even though Openkirin does not support TWRP. I would have otherwise had no option for acquiring that factory ramdisk because Huawei took them all offline.
This is all mostly just to get ahold of the ramdisk without needing to use huawei official firmware and patch it for Magisk, which there are already guides for on XDA and on Openkirin's support site. There's probably some steps of this I left out. Best of luck to others.
Resources Used that explain some steps I left out (Like installing TWRP to recovery_ramdisk, etc etc):
[Openkirin Magisk Guide](https://openkirin.net/user_guide/how-to-install-magisk/)
[Openkirin Rom Installation Instructions](https://openkirin.net/user_guide/openkirin-rom-installation-instructions/)
[Converting a TWRP Backup into a Flashable zip](https://forum.xda-developers.com/t/tutorial-create-flashable-zip-from-cwm-twrp-backup-mtk.2746044/)
[Huawei P10 Lite TWRP test build 0.5](https://forum.xda-developers.com/t/recovery-emui-8-x-huawei-p10-lite-unofficial-twrp-3-2-1-0-28-04-2018.3783447/page-2)