Database Users

Problems updating from 5.1.7 to 9

Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!

richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.

richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?

strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!

richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back

richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).

strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.

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!

.

.

HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?

HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.

.

.

HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.

.

What's the REAL method to successfully install a working TWRP, root and custom ROM?

Hi All, I have been reading various threads here and searching on Google for finding a method that truly works for successfully installing a custom ROM, getting TWRP installed and rooting with Magisk. So far, all I have found are numerous and usually contradictory methods and about 7 or 8 different versions of TWRP (so which one is completely stable and working properly?). I have tried several methods over the past two weeks and none of them are working completely.
Sometimes, I'll get a version of TWRP installed, but then trying to reboot to recovery results in a "system has been destroyed" image. Or I'll succeed in getting a custom ROM installed, but Gapps will fail with error 20 or error 70 or there's not enough space on the system partition (and I'm just trying to install the Pico version). Even I double check that the Gapps version matches the ROM version I've used, but still get an error 20 displayed.
From what I had read on numerous threads, it seemed like CosmicDans TWRP would be the one I should go with. I downloaded both of his files (the fastboot image and the zipped installer) and fastboot his "boot-recovery.img" that was specifically for fastboot only and from that recovery, I installed his "TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip". Everything appeared as if successfully installed as per the logs, but immediately upon attempting to reboot to recovery, I get the "system has been destroyed" image.
What I want to do is:
Get a working custom ROM (preferably Pie) installed
Install Gapps
Install a working TWRP (that will not display "system has been destroyed" whenever trying to boot to recovery)
Finally, install Magisk and root my phone
Can anyone suggest a site or link or a post somewhere that would explain everything correctly and is actually working? This has been a very frustrating experience. I'm almost sorry that I even bought the Mi A1. Never had any problems installing custom ROMs or rooting the OnePlus devices. All I'm left with currently is an expensive paperweight.
Thanks so much!
Cheers

From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.

Never_Sm1le said:
From your description, I'm certain that you do this on a Pie stock rom right? the installer never work on Pie stock and will cause system destroy. Just hotboot TWRP. And for the Gapps, I think it's due to the time you install it. From my experience, install Gapps after rom and before Magisk usually work. Install after magisk or custom kernel will somehow cause the same issue that you described.
Oh, in case you want to install LineageOS, you have to come to the LOS16 thread and download the TWRP from there, it's the only TWRP that can install LOS16.
Click to expand...
Click to collapse
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.

There is no permanent TWRP install for android 9 on MiA1 as far as i know.
Hotboot works just perfect.

Brianne8 said:
Thank you for your reply. When I first started the process to change to a custom ROM, I was on stock Pie. But one of the times I was wiping the device after one more problem, I accidentally also wiped Internal Storage as well. I didn't have much there since I had already backed some things up in advance. Now it's virtually empty. The steps I take are:
1. Hotboot TWRP
2. Install Custom ROM
3. Hotboot TWRP again
4. Install Gapps
This is where I usually have some problem. It's the process of installing Gapps that creates some error.
I also did attempt to install LineageOS 16 using the TWRP recovery that was linked in the post. Follow the instructions precisely I believe and now when it's time to install Gapps, I get error 64. I can't understand why. I am attempting to install "open_gapps-arm64-9.0-nano". This should be compatible with the Mi A1 with LineageOS 16 from what I am able to tell.
No matter what TWRP version I use, no matter what custom ROM I try, no matter what steps I take, there is always some issue that prevents me from completing any installation. But the abundance of so many conflicting posts don't help either. One post will state to use a specific TWRP and certain steps; another post will suggest completely different steps using another TWRP; and yet another post will provide different steps still. In some instances, there will be steps listed in the script on the phone regarding the next steps after the ROM installation that are completely different then the steps provided in the post for that ROM in the forum.
It would just be tremendously helpful to get some instructions that actually do work. As of now, I'm about ready to dump this phone in the trash bin. It's horrible. I can't even tell if it might be decent eventually since I never can get anything installed.
Thanks again for your reply Never_Sm1le.
Cheers.
Click to expand...
Click to collapse
Your reply makes me want to stay on LOS 15.1 even more. So many weird problems happen in LOS 16

I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.

Hello friend, I am currently on Lineage OS 16.0 with Magisk, Opengapps and TWRP installed. I can boot to recovery with no problems at all; in fact, I used the flashed TWRP to install Magisk.
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Note that if you are installing Lineage OS and wish to receive nightly OTA updates, having an installed TWRP as your recovery might result in a bootloop after updating. Also, if you want to manually flash the nightly update, you need to boot to the TWRP variant of @flex1911 as flashing lineage using other TWRP will result in an error. I suggest not installing TWRP when using Lineage OS.
(Source: [ROM][OFFICIAL] LineageOS 16.0 for Xiaomi Mi A1)
Regarding your problem with flashing, try to check which slot you are currently in by going to TWRP>Reboot. Keep in mind that when you install a rom, it will always be installed to the inactive slot. For example if you are in slot A, your rom will be installed in slot B. After rebooting, your current active slot will be where the rom is installed. When installing Gapps or any addons, check the slot first. However, when flashing TWRP installer, it will patch both boot_a and boot_b and this is the reason why you need to install twrp first before magisk as TWRP also modifies the boot image.
Download:
Bootable TWRP
TWRP Installer
(Both files by @CosmicDan)
Cheers mate!

rexendz said:
Here are the steps I took:
Download the TWRP boot img and TWRP installer by CosmicDan (Link below)
Copy the custom rom ZIP, TWRP installer, Magisk installer and Gapps into your SD card
Reboot your device to bootloader
Boot into TWRP using
Code:
fastboot boot boot-recovery.img
do NOT flash via fastboot
Go to Wipe>Advanced Wipe and wipe System, Dalvik, Data, Internal Storage
Press the home button and proceed to flashing the custom rom ZIP
After flashing, reboot to BOOTLOADER then do step 4 again
Flash Gapps, TWRP Installer, then Magisk Installer. You should flash TWRP first before Magisk
Reboot to system and you're good to go
Click to expand...
Click to collapse
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.

ccalixtro said:
I followed all the instructions of Resurrection Remix and TWRP is installed and magisk works perfect.
Click to expand...
Click to collapse
Hi,
Which version of TWRP did you use? There's too many. I don't know which one is considered to be the right one.

Brianne8 said:
Thanks for the lengthy reply. However, those steps do not work as you have described. Since, if I wipe Internal Storage (as per your step 5), I just deleted all the files I copied previously in Step 2. What I did, was wipe everything, *then* copied all the files and tried to install. As soon as it try to install Gapps, I get Error 64 again. I am absolutely using "open_gapps-arm64-9.0-nano" and it always fails. I have attempted 11 or 12 times already, using different slots, using different dates of "open_gapps-arm64-9.0-nano" and ALWAYS Error 64. I don't know any other version of Gapps I should be trying. The arm64 versions never will work for me.
I give up. I'll just have to stick with stock ROM. No custom ROMs will work for me no matter which one I use or which version of TWRP I use. I already wasted too much of my life with this garbage phone.
Click to expand...
Click to collapse
Copy the files to your external SD card not internal storage. But if you don't have an ext SD card, don't wipe internal storage.
Also try to check if system is properly mounted when installing gapps.
May I ask what custom rom you are trying to install?
I suggest you try Pixel Experience as it already has a builtin Gapps so you dont have to flash opengapps.

Stuck in bootloop

Hi guys,
I have unlocked the bootloader of my S5e (T720) installed Magisk and TWRP. Wiped the unit and installed Gapps + Lineageos 17.
That said: I keep booting into TWRP...
How to make the unit boot in Lineageos please?
Thanks

Seems like something went wrong with the OS installation. I would advise that you reinstall the OS again.

Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.

Yelnat said:
Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.
Click to expand...
Click to collapse
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.

OhioYJ said:
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.
Click to expand...
Click to collapse
I only deviated when it didn't work, Ironically I fixed the issue by wiping literally everything via TWRP and then trying to reinstall lineageOS. I did have a problem with it taking hours to boot the first time, but I found that I had to install lineageOS without gapps, then reboot into TWRP and flash gapps afterwards. Strange Issue but all is well that ends well I suppose.

Did you guys get a solution for this? I am in the same situation. I have the ROM and Gapps on the external card, and although I installed it again, I am still stuck in this bootloop.