Trying to install TWRP to flash a custom ROM, but still without success.
After trying the first few times, holding Vol Up + Power either booted the stock recovery or just booted android.
Then I tried to boot recovery directly through adb commands, and since then recovery is in a bootloop even if I flash TWRP again.
Is there any sollution? I also tried installinh through the TWRP app, but cant flash because it requires root and in order to get rooted I need TWRP...
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
-FliP- said:
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
Click to expand...
Click to collapse
Interesting. Have you tried Androbench?
So which version are You running right now?
Ricky_Karmator said:
So which version are You running right now?
Click to expand...
Click to collapse
I dont even remember to be honest. I think I used the base 3.1 version and got it to detect storage by starting it with the boot adb command. If I run twrp by holding power and vol up, it never detected storage.
I got the same problem with my device X820 6/64 with 19S rom, any TWRP is able to read/write on the internal storage I install TWRP from 3.0 till 3.1.1.1 . What can i do?
Thx
Aj
Related
I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.
With this modded version of TWRP you can now install A1 roms into the 5X.
How to install A1 roms using this TWRP:
https://forum.xda-developers.com/mi-5x/how-to/guide-how-to-install-a1-rom-5x-t3777139
Oreo Modded TWRP 3.2.1-0 Download:
Google Drive
Nougat Modded TWRP 3.2.1-0 Download:
Google Drive
How to install:
- Unlock bootloader
- Enter in Fastboot Mode (Power Button + Vol Down)
- Flash using "fastboot flash recovery twrp.img"
- Enter in Recovery Mode (Power Button + Vol Up)
Which one should I download?
You should install the correspondent version according to your currently installed Android version. If your current system is Nougat, you should flash Nougat TWRP. Same for Oreo. It doesn't matter which version of Android are you going to install, but the one that you already have installed. If you are in Nougat and want to flash Oreo rom, after flashing it, be sure to flash Oreo TWRP. If you dont do it, recovery may not work.
How can I use the port feature?
First, download an A1 fastboot ROM. You can do so here. Then, flash system and boot partitions using fastboot.
After you flashed it, go to "Advanced" then tap on "Terminal". Write "a1to5x" and press Enter. Wait until it finishes. Make proper wipes and reboot.
Are there any other features?
I have enabled system.img and modem.img flashing, so people without a pc can flash A1 fastboot roms. But be careful, system.img can't be a sparse image (this are the images included on the a1 official fastboot rom), it should be a raw ext4 image. You can use simg2img to convert them. Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you. I know it is not a very easy process, but at least people without pc now have a chance to update their phones.
In what roms does it works?
I have only tested it with official Android One Oreo rom, however, it should work with Nougat Android One and with custom roms. Try it and let me know in what roms does it work.
How do you port A1 roms to the 5X?
I have been asked this question a lot of times. I can't give a step by step guide since I don't have enough spare time to make a decent guide. If you are interested on the porting process, take a look at /sbin/a1to5x (inside twrp ramdisk), it is the script which takes cares of the automatic porting process. Inside it you will find how the ports are made.
Where is the changelog?
You can check it here
Donations:
If you like my work and want to contribute, you can donate via paypal.me/aex12
Device Tree: https://github.com/Aex12/android_device_xiaomi_tiffany
Manifest used: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
XDA:DevDB Information
Modded TWRP 3.2.1, Tool/Utility for the Xiaomi Mi 5X
Contributors
Aex12
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Stable
Current Stable Version: 3.2.1
Created 2018-03-07
Last Updated 2018-03-08
Reserved
Love Man... You Are Love Brother
is it normal that the external memory is not shown?
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
vangame said:
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
Click to expand...
Click to collapse
Forgot to mention it on the thread. Thanks for reminding, I am updating it right now. You should only flash system and boot. Modem and other firmware partitions can be flashed too, but they are not mandatory.
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Awesome work @Aex12. Thanks a lot
Hello can I use it at tissot bootloader?
eurekaseven said:
is it normal that the external memory is not shown?
Click to expand...
Click to collapse
That was somthing I also have noticed.. without sd memory being shown I can't do a backup to SD Card.
Instead I'll have to do a local backup and connect to PC and copy files over, Early stages I guess we are lucky we can even see the Internal Memory right?
Alright so I was curious and thought I'd see what happens if I flash recovery Nougat Modded TWRP 3.2.1-0 ( While currently running Oreo )
I booted into recovery and instantly discovered that you no longer even have access to internal memory 0b shown.. Don't waste your time !
I flashed recovery Oreo Modded TWRP 3.2.1-0 using fast boot as you won't be able to flash a recovery rom using TWRP in this state..
https://www.xda-developers.com/how-to-install-twrp/
Shows an easy guide if you aren't sure howto do this
Can not get back to MIUI Nougat or even get old recovery to work
When i try to install back xiaomi.eu's miui rom after installing zip and do all the proper wipes, it reboot to system but says that encryption was interrupted and can't complete. So I tried to install back the nougat 3.2.1 recovery and try again, with the same result. again i tried to install the rom again with 3.1.1 recovery and same happens. With nougat recovery it can't mount any partition, so it can not opperate properly, only the oreo recovery works. the only rom that works and gets installed good is the oreo one that you submitted so what can i do to get back to my normal twrp recovery (no oreo) and to a miui rom? thanks
P.D: I also tried to flash with fastboot a a1 nougat rom and with the 3.1.1 twrp port it but no succes as it can no longer mount anything, only oreo twrp is working but still not get to work properly any other rom, via fastboot or via recovery. Bootloader is unlocked.
What phone and model is this 4? It states nothing
hi,
i tried to flash system.img from official MiA1 fastboot ROMs today but i got these message " target reported max download size of 536870912 bytes, is this a normal message? will the flash resume?
vangame said:
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Click to expand...
Click to collapse
I want to know this too!
Aex12 said:
Aex12, Brother Please Fix SD issue... Cant flash files from my SD Card.
Click to expand...
Click to collapse
Comparing fstab with stock recovery / sd supported recovery might fix this issue...
This recovery doesn't read my SD card. Only the internal storage.
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
udaan said:
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
Click to expand...
Click to collapse
Make sure to make a backup of your current modem, just in case.
It's from v9.5.9.0: https://mega.nz/#!UAhwAQLY!-8np_yuZnJscEUFh9bJuCkkqDkPuZrr8Aa6o0kkBq5Q
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
tuhi009 said:
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
Click to expand...
Click to collapse
I think you need to fastboot flash boot image first, then go to twrp and flash it again from it.
---------- Post added at 08:14 AM ---------- Previous post was at 08:06 AM ----------
@Aex12 please update TWRP. I can't format /data /system etc from twrp made for MiA1(MohanCM's) but I cannot do it with yours. I have mi5x and it is ****ing stuck on boot. If I flash MiA1's fastboot rom I can get to fastboot and flash TWRP (since the bootloader is locked) but I can't do anything with your TWRP. But I can also flash MohanCM's twrp and I can do all that stuffs except for installing ROms and booting to it. im ****ing confused myself.
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.