Database Users

Android 7.1.2 Encryption

Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.

I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….

I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.

Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !

Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.

no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,

The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused

I am not using password at boot. I only set a password to unlock the phone after boot.

Miui 10 Android Pie Beta is Released For Mi max 3

hi you can grab download link from here
https://www.xda-developers.com/android-pie-beta-xiaomi-mi-max-3/

google play store keeps stopping =/

Hi,
I do assume that if I install this, I will get a device that is ARB protected.
Can you confirm that ?
Regards.

Moirae said:
google play store keeps stopping =/
Click to expand...
Click to collapse
i think its china rom and because of that play service stops:/
i cant even flash it...

I think we have to download google apps from the mi store and change permissions for it to work.

Can someone send Bigota link for 8.11.27 OTA? Thanks

NexusPenguin said:
Hi,
I do assume that if I install this, I will get a device that is ARB protected.
Can you confirm that ?
Regards.
Click to expand...
Click to collapse
ARB yes

Has anyone used https://opengapps.org/ to install all Googly things with this ROM yet.

There is no download link
Ignore me I found it? How long does it take to boot? Used red wolf and was on miui.eu latest?
flashed using red wolf was ok but stuck at boot logo. the dots are moving but rom is not booting up

Im using this new pie rom for hours and its super smooth and fluid
full screen gestgures are now super fast and with no stutters
flash this rom and other official miui zip roms using nijel8 twrp recovery otherwise it will not boot

pejji said:
Im using this new pie rom for hours and its super smooth and fluid
full screen gestgures are now super fast and with no stutters
flash this rom and other official miui zip roms using nijel8 twrp recovery otherwise it will not boot
Click to expand...
Click to collapse
going to try this now lets hope you are right as i have tried everything else and various combinations to get this booting...........
it didnt boot so starting to think this is fake rom. i tried clean flash on miui.eu rom then flashed stock gobal and clean flashed again. used this recovery and same results. it sits on boot screen with the dots flashing and nothing else happens...........how long did yours take to boot?

shingers5 said:
going to try this now lets hope you are right as i have tried everything else and various combinations to get this booting...........
Click to expand...
Click to collapse
try it and if didnt boot here are my steps if i remember correctly :
-flash latest global developer fastboot rom with mi flash (flash all , be careful with locking bootloader accidentally )
-wait until first boot before phone setup and don't go through it
-reboot to fastboot mode and flash nijel twrp
-reboot directly to recovery
-wipe->factory reset
-flash 8.11.26 pie
-reboot system

Exatly as for me. Flashed with nigel TWRP, with format data before. Few issues but CN firmware... Google must be installed.

ok will do that now and report
i flashed latest global then tried to flash with that recovery but nothing.
i am now going to flash china dev latest and try again
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
so to be clear
i am gonna flash dev global 8.11.23 via fastboot
then wait for it to get to 1st set up screen but not go through the setup process
will then flash that twrp you mentioned via fastboot
and flash the rom after factory reset

shingers5 said:
ok will do that now and report
i flashed latest global then tried to flash with that recovery but nothing.
i am now going to flash china dev latest and try again
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
so to be clear
i am gonna flash dev global 8.11.23 via fastboot
then wait for it to get to 1st set up screen but not go through the setup process
will then flash that twrp you mentioned via fastboot
and flash the rom after factory reset
Click to expand...
Click to collapse
i did exactly what you said again just to be sure
and it booted up with no problem
- mi flash->global 8.11.23 -> clean all
- first boot until welcome screen
- power off-> volume down+power -> fastboot and run "fastboot flash recovery nijeltwrp.img"
- volume up+power to boot to recovery
(so far if decryption goes well twrp shuold not request decryption password and you could mount data and see internal storage contents in /sdcard with no problem in twrp file manager)
- wipe->factory reset
- install pie zip rom 8.11.26
- wipe dalvik+cache
- reboot system
it took about 4 or 5 minutes for me to boot

If I've gone straight from the latest stock China ROM to xiaomi.eu 10.0.0.6.0 and have since flashed the latest nijel TWRP - which is all working fine.
Can I simply flash to this pie release or do I need to have previously flashed one of the developer ROMs?

Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!

eresen said:
has anyone used https://opengapps.org/ to install all googly things with this rom yet.
Click to expand...
Click to collapse

nijel8 said:
Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!
Click to expand...
Click to collapse
You can't decrypt it anymore!

nijel8 said:
Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!
Click to expand...
Click to collapse
first thanks again for your great work on this recovery
decryption was good with oreo 8.11.15 china rom but right after pie rom boots and rebooting to recovery, decryption fails
from there rebooting to recovery again doesn't change anything ... recovery asks for decryption password every time.
and cuz data partition is not mounted so recovery log will not be saved to internal memory to attach it here
after formatting data miui boots successfully and encrypts data again.setting up the phone and rebooting to recovery ... but same thing happens and decryption fails.

Oneplus 5 hardstuck bootloop. Please help me out, I've tried everything!

Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!

You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.

Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!

BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190

strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.

BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?

strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)

BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk

strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop

BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop

My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter

BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up

strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!

BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?

strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!

PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!

BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter

Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!

Questions about upgrading Lineage OS 16 to 17

Hello,
I do have some questions about upgrading LOS from 16 to 17, maybe someone can help me bringing a little light into this upgrading process.
- Is the sideload way the correct way to do this? ( https:// wiki.lineageos.org /devices /fajita /upgrade)
- What´s about the play services, I dont have any installed ( ..."If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them"...) So if later on I want to install e.g. opengapps I have to wipe all my data after upgrading to 17??? (How? TWRP - wipe -advanced wipe - data and cache ???)
and what´s with all may data? I have titanium backup pro (no SD card), so I backup may phone, put it to my PC, upgrade to 17, wipe all data, put the backup back to phone and reboot?
Or do I have to install Magisk.zip and titanium.zip from within TWRP again first
- What do I do if the sideload fails?
- Can I do the upgrad process with TWRP too? (copying and installing from within TWRP?)
- And what about with the A/B slots, no installing twice on both slots?
As you see, I am unsure on how to do things right and I only did this once before as I installed Lineage OS.
(This would be the way I would do this:
- backup all data to PC
- Boot into TWRP
- copy LOS17.zip. Magisk.zip and Titaniumbackup-pro.zip into internal storage
- install LOS17 and boot into TWRP
- wipe data and cache
- install magisk and TB
- copy all data back and restore? (only user data or the system data too??))
Maybe someone can help me with this. Thanks!

My guide for installing Lineage maybe helpful: Guide Installing Lineage
I would recommend a clean install. Most that have tried to follow that wiki have had issues (if you look in the LOS thread). I haven't used. TB zip, but I did use my TB data from the app without issues. If you dont use Gapps, just dont install them. Skip that step. You still have to reboot to recovery to install Magisk though. I dont think I would try a TB zip until after the first boot.
Installing twice is for the intial install to get the same thing on both slots. You dont want Android 9 on one slot and Android 10 on another, or LOS 17 on one and OOS on another. Once you have LOS 17 on both slots and go to update you will just flash once. See my guide about doing an update.

Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.

KKF32 said:
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
Click to expand...
Click to collapse
How did it go?

badpanda said:
How did it go?
Click to expand...
Click to collapse
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
So I thought maybe the "no factory reset" at the beginning may caused this problem, so I started the whole flashing again.
Long story short: Being distracted I once forgt to flash TWRP after the LOS and now I am stuck in fastboot.
Cant get anymore into TWRP, "fastboot boot TWRP.img" always throws me into fastboot forever wait
Tried to flash TWRP direct from fastboot "fastboot flash recovery twrp.img", always get a write error.
So, at the moment all I can get in is the bootloader, and I have no clou how to get TWRP up and running again.
Edit: Managed to get into TWRP again, but this double flash + Magisk always gives me this "Qualcomm Crashdump Mode"
Help would very much appreciated!

KKF32 said:
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
Click to expand...
Click to collapse
So you tried to go straight to LOS 17, used an old version of TWRP, and never wiped data while going between Android 9 and 10? None of that will work. I think didn't make it clear, you need you need to be on the OOS 10 firmware first. Flash OOS 10 to both slots, at this point using the fastboot ROM would be my suggestion, like my [Guide]Installing Lineage.
Once you have Android 10 in place one both slots, then start your OS 17 install. Note there is a cliff notes version of that guide in the second post, if you don't want all the "wordy" details.

Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.

KKF32 said:
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
Click to expand...
Click to collapse
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.

OhioYJ said:
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
Click to expand...
Click to collapse
So, LOS17 is up and running, I did it the long way but good to know the fastboot Rom method now. I confess some part of this thread would not have been necessary if had read your installations instruction carefully....
So let me thank you for patience und help, "Reading broadens the mind", I often tell others, will remind myself nexttime

"No OS installed" after successful custom ROM flash

Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.

fixed by @hainguyenthao, thanks ^-^

turtpipchim said:
Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.
Click to expand...
Click to collapse
try my kernel
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com

turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
can I ask how was it fixed? I have the same problem with A6+ Samsung device. thanks

turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
How?