Database Users

Solution for TWRP 2.8.x 6.0+ Custom Rom flashing problem

Hi all! I'm new here (at least at account level) and with my first thread I want to help people which can't flash 6.0+ roms in official 2.8.x TWRP for our Moto X 2013 (like @dziarski in TWRP 2.8.7.0 thread).
I have Moto X 2013 (XT1052 model for reference) and I unlock bootloader, root and put costum roms not so long ago but here out to resolve this.
You need to upgrade your TWRP because TWRP <3.x don't support 6.0+ rom flashing well (edit: mochi579 below report twrp 2.8.7.0 can work for flashing too even I recommend latest 3.0.x version for avoid all problem especially with 7.x roms). I advice you to check out unofficial TWRP 3.0.2-0 by fantastic TeamMEX here.
This updated version grant you to flash both 6.0+ and 7.0 roms (tested myself) without any error.
There are my ROMs test to try this TWRP:
Legenda: (Android version)
TWRP 2.8.6.0 official:
Resurrection Remix 5.7.4 (6.0.1) -> failed immediately with this error
Code:
E: Error executing updater binary in zip "/..."
Error flashing zip "/..."
After some research I understood I need to updated my TWRP and here's the result
TWRP unofficial 3.0.2-0 by @TeamMex:
RR 5.7.4 (6.0.1) again -> succes without problem (I use right now)
CM13 (6.0.1) -> succes
CM14 (7.0) -> succes
OctOS Oct-M (6.0.1) -> succes
Xperience 11.0.0_rxx (7.0) -> succes
All succes without any error during flashing.
Just in case I want to add my step even its very common:
1) Make a NANDroid backup if I don't have it already
2) Wipe Cache, Data, System, ART/Dalvick cache
3) Optional factory reset (cache,art/dalvik and data)
4) Flashing ROM + Gapps from OpenGapps (remember to select ARM)
5) Reboot and finish
If there's a problem in the post or its wrong place (its here or Q&A) please let me know

Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.

mochi579 said:
Thank you WOrld1. But I'm flashing cm13, cm 14 & xpe 11 using TWRP 2.8.7.0 and it's working perfect except some known bugs.
Click to expand...
Click to collapse
Hi,
I was using 2.8.6.0 because in the root thread by Kidjoe here in General he write about a possible read error about SD card in the phone (clearly a bug because we don't have it xD), so my experience with 2.8.7.0 is zero unfortunately but I think it's very similar.
I have zero problem flashing the rom I listed, for various reason some mod I flashing more than one time (never because flashing problem, usually rom itself problem or just jumping back and forth).
I flash xperience 2 times, cm13/14 and OctOS one time and Resurrection Remix many times if we include backup when coming back from these ROMs.
The only know bug I experienced in 3.0.2-0 is slow flashing in "normal" condition. Just follow the note in the op of recovery thread:
Code:
NOTE: If you have slow format on ext4 go to Settings->Use rm -rf instead of formatting
Copy pasted from TeamMEX thread.

Tab 4 LTE SM-T535 recognized as matissewifi

SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation.
Hello everybody,
I recently bought a secondhand Galaxy Tab 4 SM-T535. It has the android stock rom 5.2 and I wanted to flash a CM or any custom rom to speed it up a bit and remove all pre-installed apps. I did flash TWRP through Odin and it works fine, then I copied Gapps for 7.1 pico versión and crDroid custom rom based on LineageOS 14.1 and nougat 7.1 for matisselte aka Tab 4 SM-T535. I followed instructions (that are pretty the same for every custom rom) so I wiped dalvik, cache, system and data, then I flashed (tried to) crDroid 14.1 zip and... TWRP says something like: unable to flash zip, it is for device matisselte but this is matissewifi. Wtf?! So, ok. I thought I'm blind and I got the wrong version, I downloaded the matissewifi version, tried to flash again and it did flash. Then I flashed Gapps and rebooted, now it goes directly in download mode and says Could not boot normally... What is happening? I also tried CM 14.1 for matissewifi, it flashes but can't boot and I'm unable to flash the matisselte version. Why?
it is for sure the LTE tablet, I read it in settings and info in the android stock rom and it has a sim slot, so it can't be the wifi one.
Thank you in advance for any reply. Let me know if you need more informations. Thanks.
P. S. I already searched in the forum and didn't find any similar case.

Hi,
has anybody found a solution...?
seen too late.....
"SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation. "

So glad you posted this because I had failed in all my attempts and had tried a few TWRP versions but not that one, which worked perfectly with Lineage 14.1.

Error while installing gapps for 8.1 oreo based custom rom on Potter

so i was on oreo 8.1 soak test version and wanted to upgrade to a 64 bit custom rom based on oreo. unlocked the bootloader. flashed TWRP (3.2.3-1) . Then i flashed franken rom based on 8.1 and opengapps arm64 mini for 8.1.x. everything was right until i figured out that there was no fingerprint functionality. i followed this thread https://forum.xda-developers.com/g5-plus/help/fingerprint-enrollment-custom-rom-t3804908 and first flashed the persist fix zip and then the stock 7.0 rom. everything worked fine and i was on stock 7.0 and then i tried to again flash the franken rom but this time the rom was flashed successfully but during gapps installation i got ERROR code 20 and it said something like "incompatible rom found". it was detecting the the rom as 7.1.2. but neither the stock was 7.1.2 nor the franken one and i had also wiped dalvik, data, system and cache before flashing the franken. i tried again and again but failed. what may be the problem here?
sorry for the story like description

Problem with 15.1 lineage update: I've lost all Google functions.

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.

Open Gapps 9.0 arm64 wrong architecture error

I am on a 6T and am trying to install LineageOS with Open Gapps Pico v9.0 arm64. But the Open Gapps will not install, giving an error that the arm64 Architecture is wrong. This is not correct, the arm64 is the correct architecture. I have checked with this:
Code:
adb shell getprop ro.product.cpu.abi
which shows this
Code:
arm64-v8a
Where can I get the correct one? I prefer the pico for the MINIMAL Google presence on my phone.
I have also tried MindTheGapps 9.0 arm64 but that complains the signature is not correct, and does not install
So ai can install LineageOS using the adb sideload <lineageOS.zip> method, but then not get Play Store to install a few apps.
I have also tried the rather long winded way in this post and have the same problem.
Can anyone give me a working method to Install LiknmeageOS 16 with Gapps Pico.

I have got Lineage to accept the open gapps by repeatedly installing it and TWRP and booting into recovery 3 times, leaving the Gapps until last before doing a proper boot.
However now I just get the logo, and no OS, then it returns to the TWRP recovery.
I am not new to this, this is the 5th device I have used for LineageOS, but never had this bother before.
Any ideas?