Related
Hi everyone!
This is my first post, hope there is a solution.
I have Samsung Galaxy A3 [A300FU].
I wanted to get rid of branded firmware, so I've found stock ROM here: mrcrab.net/stockrom/sm-a300fu.html and flash it with Odin and it was ok.
Then I wanted root, so I've followed this guide: trueandroid.com/root-samsung-galaxy-a3-sm-a300f-easy-guide and now, whenever I restart the phone, it boots to the screen with yellow text: set warranty bit : recovery (file_1.jpg). Then it goes to the screen with opened green robot (file_2.jpg) and after I choose: reboot system now, it loads to OS normally.
How to fix it?
Ok guys, I don't know what happened, but I've managed to save the day
What I did was connecting my phone to KIES and select Firmware Update and Initialization from the Tools menu. It wipes all the data so be prepare for that. This helped to get rid of the yellow text on the screen while booting, but the phone still kept booting to the recovery mode.
Then I've installed TriangleAway from this thread: forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114 but it didn't seems to work (and, by the way, it doesn't support my phone). I've also installed SuperSU from Play Store, and also didn't work, so I've uninstalled both and reboot the phone. And guess what - it booted normally, straight to the OS.
Magic.
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
Hello, I recently bought a A3 as well and im quite dissapointed to see there are no custom roms or forums dedicated to the A Series (A3, A5, A7). Ive been itching to root and install a custom rom seeing the stovk is starting to slow down a A LOT! Could you help me out by guiding me through the bloatware removal as i dont want to uninstall something i shouldn't
Sent from my SM-A300FU using XDA Free mobile app
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
You flashed a custom recovery meant for Galaxy Alpha on Galaxy A3? Doesn't doing that bricks the device? I'm having the same problem too.
Sent from my SM-A300F using XDA Free mobile app
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Is TWRP 2.80 Working?
locovibe said:
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Click to expand...
Click to collapse
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Etnad07 said:
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Click to expand...
Click to collapse
Well, it seems it only solved yellow text and can't boot into recovery at all. It can't be that way! So!
I've installed unbranded software once again and was waiting to update to Lollipop via Kies. But it took so long that I couldn't resist to root, but I did it differently this time. I've found KingRoot app which works like a charm. Just download the apk [mmgr.myapp.com/myapp/Kingroot/webapp_kingroot/image/KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk] from [kingroot.net/down#root], run it and voila! No hassle, no Odin. After rooting there will come up two apps: Kinguser and some app in Asian. I've uninstalled the second one - it cleans memory and stuff. Stock recovery stays untouched and booting is normal.
Hi Everyone!
I Hope There Is a Solution....
I have galaxy a500g running with stock lollipop and I need to install a custom rom so I flashed TWRP_2.8_SM-A500-LL.img and booted into recovery once it booted into recovery it struck at set warranty bit:recovery and struck at recovery loop....is there a way to install a working custom recovery for galaxy a500g
Thanks in advance
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx
Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F
I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.
Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)
I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped
SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight
Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best
Just got it today. Couldn't find a trustworthy/safe method to root it.
yo!! its easy, download the latest super su, the latest TWRP and the latest odin, now put the super su flashable sip on your SD or internal storage, now go to download mode, wait to see the added, this is important, UNTICK auto reboot, now flash the TWRP, make sure to untick auto reboot, when the TWRP is flashed take out the battery, now turn on the phone in recovery mode, dont let the phone start normaly, now in the TWRP recovery go to install and flash the superu su zip, wait to it over, and reboot, done your note 4 n910u is rooted like mine
press thakns if i help you hehe, i want to make a tutorial but i think i cant upload images yet
Thanks a lot. Another thing, does using Odin removes all data & apps?
nope, you dont need to do any wipe
Alright. Thanks a lot. Another thing, is yours Marshmallow too?
I did everything as you said. I pulled out the battery after flashing TWRP, but when I tried to go to recovery menu. My phone keeps getting stuck at the 'Samsung GALAXY Note 4' logo and there's a red message in the top left corner that says, "RECOVERY IS NOT SEANDROID ENFORCING."
which twrp version your flashed?
im at mm u1dpf1
twrp-3.0.2-0-treltexx.img.tar
The problem's solved. Not sure what caused it at first. But I got the TWRP flashing done. Took me 3 tries.
might some drive missing? i did at the fist time, i dont read any guide i just remember a time i root an samsung mega 5.8, and use this method, i have asked to how to root my note 4 and no one help me, so i decide to take the risk and try it, and i done whit it, now enjoy the root acces bro
Tnx a lot for your help. I appreciate it!
So, I will preface this post with: I am a noob. I am not very well-versed in technology or costumizing Stock OS, I can use a Stock OS on any Android phone, but as soon as anuthing resembling Coding comes into the picture I may as well be trying to learn how to operate Alien Technology.
So heres the problem: I tried to Factory reset my Samsung Galaxy J7, which had Developer options activated, OEM unlocked priopr to the Samsung Updcate that put Oreo 8.1 on it, so I did have an unlcoked Bootloader. My Boyfriend (Who very much enjoys tinkering with tech-stuff, nd is usually highly proficient at such endeavors) insisted I do some kind of backup, even though I had preveiously backed up everything to my Samsung cloud; I handed my phone over to him and when I got it back it was stuck in a Boot-loop, he said it was Softbricked. So, we did much research to try and get a custom ROM after installing TWRP 3.2.3-0. I decided on a Prometheus OS ROM, and downloded it aswell as the GApps for my phone (ARM+7.1 since the new ROM is a 7.1 OS). I folowed the instructions precisly; but even still it is in a Bootloop, and Idk what to do now, my Boyfriend says he needs to edit the coding on the OS ROM, but this Prometheus ROM is the first one out of countless that has made it past the attempt at installing (Usually I get to the point where I 'Swipe to install' then after a few seconds of instalation it reboots into TWRP as if I didnt do anything; or gives me an ERROR 6 or 7, but this time it says "Instalation compleate, Reboot now?") So, Idk how to fix it but I really really like my J7, and I want to fix it.
Device Specs:
Model: SM-J727R4 Galaxy J7 2017 LTE-A
Model#: j7poplteusc
Original OS: Oreo 8.1.0
CrookedYoungHeretic said:
So, I will preface this post with: I am a noob. I am not very well-versed in technology or costumizing Stock OS, I can use a Stock OS on any Android phone, but as soon as anuthing resembling Coding comes into the picture I may as well be trying to learn how to operate Alien Technology.
So heres the problem: I tried to Factory reset my Samsung Galaxy J7, which had Developer options activated, OEM unlocked priopr to the Samsung Updcate that put Oreo 8.1 on it, so I did have an unlcoked Bootloader. My Boyfriend (Who very much enjoys tinkering with tech-stuff, nd is usually highly proficient at such endeavors) insisted I do some kind of backup, even though I had preveiously backed up everything to my Samsung cloud; I handed my phone over to him and when I got it back it was stuck in a Boot-loop, he said it was Softbricked. So, we did much research to try and get a custom ROM after installing TWRP 3.2.3-0. I decided on a Prometheus OS ROM, and downloded it aswell as the GApps for my phone (ARM+7.1 since the new ROM is a 7.1 OS). I folowed the instructions precisly; but even still it is in a Bootloop, and Idk what to do now, my Boyfriend says he needs to edit the coding on the OS ROM, but this Prometheus ROM is the first one out of countless that has made it past the attempt at installing (Usually I get to the point where I 'Swipe to install' then after a few seconds of instalation it reboots into TWRP as if I didnt do anything; or gives me an ERROR 6 or 7, but this time it says "Instalation compleate, Reboot now?") So, Idk how to fix it but I really really like my J7, and I want to fix it.
Device Specs:
Model: SM-J727R4 Galaxy J7 2017 LTE-A
Model#: j7poplteusc
Original OS: Oreo 8.1.0
Click to expand...
Click to collapse
Reading that was a bit if an eye attack, one massive hard to read block of text.
To install a custom rom you need to first FORMAT (not wipe) in TWRP.
Then immediately after the install (assuming it installs correctly this time) you need to install Magisk.
ashyx said:
Reading that was a bit if an eye attack, one massive hard to read block of text.
To install a custom rom you need to first FORMAT (not wipe) in TWRP.
Then immediately after the install (assuming it installs correctly this time) you need to install Magisk.
Click to expand...
Click to collapse
Sorry for the text block, I was stressed lol But there was a misscommunication on my part tbh; in order the steps I took were
-Transer downloaded ROM to SD card from Computer'
-Boot into revovery via TWRP
-Format
-Install ROM
-Reboot
-Install GApps
-Wipe Davlik/cache
-Reboot
then, the screen turns on to the default "Samsung Galaxy J7" Bootload, flashes blue for a millesecond then goes dark, and then repeats for all of eternity. And about the Magisk; the ROM installer has an option to install Magisk or SuperSU ROOT, do I need to additionally add a Magisk file? i had checked the option for Magisk last I attempted to flash the ROM
CrookedYoungHeretic said:
-Transer downloaded ROM to SD card from Computer'
-Boot into revovery via TWRP
-Format
-Install ROM
-Reboot
-Install GApps
-Wipe Davlik/cache
-Reboot
Click to expand...
Click to collapse
Nope.
Format
Install rom
Do not reboot.
Install magisk v18 zip via twrp.
Reboot to android.
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.