Database Users

[Q] Stuck in TWRP, Tried everything i could find about it!

So this is my story,
I had a stock rom lg g2 d802 phone working, but didnt had a micro sim yet so i decided to flash a nice rom (http://forum.xda-developers.com/showthread.php?t=2505682). So i followed everythin as described, but then... when i finishd flashing the rom i noticed that nothing has changed in the lg. it was still the same with everything on it as before.
So my stupid brains decided to make a Wipe! in TWRP (the one where you need to type yes to continue) and after that reflash the rom i wanted. So i did just that, resulting >>> a clean sweap on my phone, everything was gone, even the rom i put on the sd card.
Not that big a deal, i just use ADB and push it on my phone, (did just that) and in TWRP i installed the rom, everything goes as supposed to. But when the reboot promt comes and i reboot to System, im getting back to TWRP.
I tried to flash the following
1. A backup i made of the phone (no result)
2. flash rayglobe (http://forum.xda-developers.com/showthread.php?t=2493209, no result)
3. flash the previous rom (no result)
at step 2 tho (rayglobe) when i flash it, i get the installer and work my way trough it, when i reboot my phone it gets back to TWRP (offcourse) but then i notice changes, like i put my ray.zip in /sdcard/ and its gone (cant see it) but i can still press the space where it was before, and it will display the pressing-animation, but wont do anything else.
i also restored my /boot folder with the one in /boot (phone side) thought it might help. no result
Then i moved on to the LG mobile support tool and put the phone in download mode (firmware update) the tool recognizes the phone but it gets stuck at step 2 (the download part) and the text in the tool isnt updated (displays chekking pc status) while in the download part. around 14 sec in from starting the upgrade in the tool. so this has no result 2.
i have tried drivers from:
google android
google sdk manager
lg android driver
lg united mobile driver
universal adb driver
with some i cant do adb and with some i can, also with some i cant do sideloader and with some i can.
but with all i cant do fastboot.
as of now i have 4 "boots" i can get into
1. recovery (TWRP)
2. download (firmware update)
3. reset factory settings
4. hardware key settings (to use buttons as phonecall helpers )
summary:
i can boot into TWRP and flash/instal/backup but with no result
what i want?????
I WANT MY STUPID BRAINS REMOVED, also i want to get back to stock or any rom that works (pref stock, got backup via TWRP) asap.
how do i manage this?
so feel free to to help me out here

going to c captain america, will be back in a while, please please please help me out

[Q] LG G2 running CM12, no recovery or download mode, need help.

Hi guys,
I attempted to restore my G2 (D802 international 32GB) back to the stock kitkat firmware from Cyanogen Mod 12. While attempting the restore, the lg support tool gave me an error saying it had failed, however when I disconnected the device it was apparently still doing something.
I now am at a stage where I get no recovery, download, or fastboot mode, etc, however my device is connecting to my PC as qhsusb_bulk in device manager. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2582142 in order to help remedy the issue, however it didn't work. I'm guessing it could have something to do with the fact that I had CM12 rather than the stock firmware of which I extracted the necessary files for my device (I extracted the files from an IMEI number provided KDZ) in place of the files provided on the thread.
Could someone help point me in the right direction? Do I need the image files from CM12, or the stock images despite the device running CM12 before hand? am I following the right process?
Thank you very much in advance for any help anyone can provide, I really appreciate it!
PS. Sorry if this has been covered before, I just haven't been able to find anything else.

Were you able to find out what the problem was? I am on CM12 myself on my G2 D802. Got some problems with TWRP. It wouldnt restore backups, and had problems with flashing ROMs ang gapps so I flashed CWM with flashify and now when I try to reboot to recovery I just get the LG logo and boot verification issue... Would really appreciate if you could share your solution if you were able to find one

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.​
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)

reserve 1

reserve 2

reserve 3

reserve solution 4

reserve solution 5

Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.

https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.

Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated

Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.

Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!

aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++

I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think

Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.

I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.

Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!

Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.

LG v20 H918 Stock recovery+rom?

So I just recently wiped all the data on my phone in a rush except TWRP and I want to revert back to stock ROM. But LGUP doesn't recognize my phone when I do use TWRP or fastboot mode. From my research done I need to get stock firmware update back in order to get LG UP to work again? I'm not entirely sure what I'm doing since I'm new to this. Help im noob. no backups too.
I tried this thread:
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
But... LGUP doesn't see my device as said and KDZ files don't flash on TWRP. I tried doing some random .ZIP files of stock roms which I'm not entirely sure I did correctly.

You dont use TWRP or fastboot with LGUP you use Download mode

me2151 said:
You dont use TWRP or fastboot with LGUP you use Download mode
Click to expand...
Click to collapse
Yes I know that. But TWRP replaced my download mode because whenever I plug in my device and press the UP volume key TWRP showed up instead.
Anyway I fixed it myself so thread close pls. Not sure how to do this.

Whenever you fix your own problems, it's still considered good forum etiquette (to many people including myself) to still offer the solution you came up with so that anyone else reading the thread because they might be having the same issue that you're having would love to get a working solution too.
Anyway, the issue is that the lafsploit method using the USB Linux distro overwrites the laf partition to get TWRP installed on the device. Most people never bother to fix that problem but the solution is to flash the laf_restore.zip file (I got it from another thread but can't find that thread at this moment so I'm just going to host the file on Drive for safekeeping):
https://drive.google.com/open?id=1WkR-6--OpOaRw-W5Wt9BzljIBVvG_kMF
MD5: 976bf936548c6fab4fe04dec43f53fb4
SHA-1: 1c6d509f4f29b65d7e0d3d406e6978caeb43d6a9
After you flash TWRP temporarily on the H918, then update TWRP (flashing the newest version), reboot back into recovery/TWRP and then flash the laf_restore.zip which will restore the laf partition(s) to their proper state - AFTER all this then you should be able to get to Download Mode again normally if you must.

Oh yeah I was sorta thinking about posting my solution last night. Anyway the solution I found was to find a .ZIP file of an older stock ROM like the H91810u using what I used which was TWRP since I didn't know what else to flash it with.
I found the file on this thread IIRC. A lot of the links are dead but the 10u version wasn't for me.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
My main concern was to just get stock ROM back. I only wanted stock recovery because that was the only way I knew to flash .KDZ files using LGUP. Although I guess bootloader is still unlocked on my phone. But stock download mode still comes back.
I didn't do anything after that but it seems good enough for me now since I don't turn turn off and on my phone a lot. Till another day.

lineage 17 on samsung galaxy a20e

there are some instructions how to install twrp or lineage on nnthe samsung galaxy a20e. it took me a while to manage it, for one part because it seems sometime i did not do everything exactly like it was described (old fault of mine...) sometimes i found some explication in another instruction.
this is why i post my experiences, to encourage those who also struggle with problems, don't hesitate, sometimes it only takes a bit longer, but also because some things i still don't understand, maybe somebody can explain me what happened..
naturally, firsty of all i first had to install twrp. so i searched for instructions and found some, including liks to download the twrp.tar for my model. some of them i was able to flash by odin, but when i then restarted the phone it only showed a black screen with some pink in the middle, with some fantasy i could read a slight samsung or samsung a20 in it. this happened when i tried to restart in recovery to flas disable-dm-verity, also when i tried to restart direct to system. with all the attempts i got very experienced in flashin back stock rom...
then i found a working recover after restart to recovery i got my twrp screen and was able to flash the no-dm-verity or magisk.
so next i tried to flash the lineage (unofficial lineage 17.zip) but always got the message invalid zip format. tried to unzip and zip again but no way. so i thought i might get lucky with adb sideload, entered the twrp advanced and clicked adb sideload, the screen told me starting adb sideload but the phone could not be detected by the computer. the computer detected it when switched on or in fastboot, so it seems the sideload did not really start.
so i searched the interenet for roms because i really wanted to get rid of google and a million of apps in the stock that i don't need. i found the links to andyyans gsi and several other zips.
as i was not used to the gsi installation i thought i better stick on what i know and tried to install another zip. but most of the time i got the invalid zip message or the zip is for another phone although i downloaded it for the a20e. but then twrp accepted the crdroid.zip (eureka) i downloaded, i was very happy, after the instalation was finished i restarted the phone and the screen went black, turned off and it seemed not pressing to download, to recovery or to start changed anything. i also tried with pressing vol up, vol down and conecting with computer but also no downloadmode started. so i pressed very long always several buttons and after a while the phone vibrated by pressing long vol down and power, but no screen. after it vibrated sometimes like this i turned to vol up and power, it vibrated again and finally twrp started. although the phopne was fully charged when i started the process, it now had only 8% battery.
so i charged the phone again, flashed the stock rom and twrp to try again to find a solution. at this time i also found an instruction that explained why after flashing twrp the system can't recognize the folders (downloads, music... ) and only gives them combinations of letters and ciffers, i have to decrypt it in twrp, wipe, format data, yes and this problem is solved. i don't know it happens always and who made the instructions to flash twrp thought this is common knowledge but in the first innstructions i read it was not mentioned.
i tried again to flash zips and now got a funny eroor message from twrp, unable to zip, this zip is for a20 but this phone is a a10. i tried another zip, the installation started and in the text i could see that it was for a10... so somehow twrp was sure to live on na a10, how could this be??? i thought maybe the twrp was for the a10 (it was a 3.4.x), so i again downloaded a tar directly from the page of twrp for the a20. but when flashed this twrp (3.5.x) and tried to restart to recovery (or to system) the phone was still in downloadmode and refused the custom rom. i had to flash back to stock, then flash again the twrp3.4 that thought my device is a a10, then i could flash the new twrp3.5 i was sure it was from the original site and for my device. i don't know the 3.4 was patched, i got the downloadlink from one how-to-site, but i did not read anything that it was patched...
but after testing all the zips that did not work, and also with the new twrp i was not able to sideload i decided it is time to learn how to handle the xz. so i extracted first the lineage 18, installed it by clicking install image (after wiping) but again the phone turned black and i had to press a while to get twrp restarted and the battery again was nearly down.
the same process worked with the lineage 17, so this is what is now innstalled. both where the correct ab versions, i checked before with treble info what version i need.
so, can anybody explain me
-what happened with my battery when the phone turned to apparently death?
-why could twrp think my phone is a a10, would a twrp for a10 work on my phone?
-is it possible that the sideload feature does not work on this phone?
¡¡¡and many thanks to all those who upload roms and instructions so people like me can make their phones a bit more like they want them!!!

The first time I flashed my A20e (SM-A202F) had the same problems with finding the right TWRP. I cannot answer your questions, but I can tell you what I do.
Beforhand: unloock the bootloader. Upgrade to the latest Samsung firmware. Download AndyYan's 18.1 LineageOS GSI arm64_bvS. Thought arm64_bvS-vndklite can work as well, I found that bvS has less bugs.
After installing the Samsung drivers and the adb stuff on a PC with Windows, I install Odin and flash with Odin the attached TWRP (AP), while phone is in Download mode.
I then go to recovery (TWRP) and if the folders and files are encrypted, I format, then yes. I wipe 4 things: dalvik, catche, system and data.
I then move the GSI image file inside the zip (not the zip) by drag and drop on my PC. Then in TWRP I click install, select image, not zip, select system and flash. Then I reboot to system.
I never had any problems with this installation process. The bvS has a bug with the Lineage music app, but simply install a local music app, such as Musicolet or AIMP from the Aurora Store (from F-droid).
On the camera side I haven't seen any app that significantly improves photo quality. My recommendation would be FreeDcam from F-droid. Use it on special occasions, as it tends to heat the phone.