Related
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Make sure everything is formatted as ext4 and update firmware to 3.6.1 just to rule it out.
I would use the latest twrp.
I go to format tick all the boxes and clear everything then go to reboot > recovery. Once back in twrp copy the ROM and gapps across from pc install ROM and gapps together, wipe cache and dalvik reboot.
I'm in the process of doing that now.
The TWRP that I'm using is 3.1.1-0 which looks to be the latest. I am working with OOS 3.5.8 but will look at downloading 3.6.1. I am working to get Lineage 14.1 on there once everything is stable.
I ran into another weird is when using the qualcomm recovery tool:
My method is to enable ADB, enable OEM Unlock, enable Advanced Reboot.
Reboot into fastboot
Fastboot oem unlock: is successful
Fastboot reboot
I then go through renabling ADB and Advanced Reboot, OEM Unlock is still enabled.
I then reboot into fastboot
Fastboot flash recovery twrp-3.1.1-0-oneplus2.img
This completes successfully and then I fastboot reboot.
I have tried several times to get into TWRP but I keep getting the stock recovery.
I have tried to reflash recovery but nothing ever changes.
Is there possibly something wrong with the OEM unlock that says it was successful?
How do I go about troubleshooting this?
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
cyrus104 said:
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
Click to expand...
Click to collapse
Internal doesn't really matter to be honest, did you check they data and system are formatted as ext4.
It is in twrp advanced wipe options.
Did it ever boot ?
I did doubt check the data and system are formatted as ext4.
I let it sit for 3-4 hours and didn't see any progress.
Try a different rom. There are a lot of lineage based roms around.
I tried that and am getting the same results. Even if I flash a full TWRP backup from a time when I had it known to be working it happens.
I've tested this with 3 different roms now. My latest attempt has been to update TWRP to 3.2.1 and then install lineage 14.1 20171208. I also tested with Paranoid and Carbon because they were near the top of my list not because I know anything about them.
The phone just never gets past the boot animation. If I reboot to recovery is there a log I can pull to see what the issue is?
Thanks
Would like to see if anyone has any thoughts. If I run OOS I can use the phone but as of right now I can't use any other rom.
Is there any advanced fastboot or wipes that can be done to get it to boot. Is there any type of debugging that will show me what's happening when it tries to boot.
Just trying to bump this, I really need a way to debug this problem. Besides running OOS, I have a feeling this device is bricked and the mega unbrick guide doesn't work.
Also looks like if I try to put Kali on top of the base 3.5.8, the phone goes into the animation loop. So any change after OOS on the device puts it into an animation loop.
Is there a way the system or boot locked? Even thought I can TWRP anything onto the phone without errors.
Hey!
I've got the same issue it seems, phone just sticks to boot animation when flashing any other ROM than OOS 3.6.1.
Any update?
EDIT :
problem was with the persist.img
Flashed a different firm file and it was resolved
cyrus104 said:
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Click to expand...
Click to collapse
OOS does not refuse to boot if a mountable partition is corrupt. This is not the case with lineage. If a mountable partition is corrupt and the corresponding fstab entry does not allow lineage to format and somehow mount it then init never proceeds
Try flashing this file: https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and try again
Note that this file reboots the device after the flash is done so don't use twrp queue to flash this file. Flash this file last
---------- Post added at 17:45 ---------- Previous post was at 17:34 ----------
Alternatively this is a method I don't recommend to beginners because they accidentally give twrp logs to devs without realising it
You can get logs by making the forcing the device to "crash" through the power button
Here's how it's done: you boot the non-booting ROM and wait for about a minute. Then press power + volume down while it's on the bootanimation. You have to hold it until you see the oneplus logo and boot to twrp
TWRP's kernel will recover the last booted kernel's log from ram and place it in /sys/fs/pstore
First you have to open the log yourself to check if it's valid. The file is console-ramoops-0. All other log files in that location are invalid for your specific issue
Now for an ordinary user this is hard. They can't tell if the log is a recovery log or a ROM log. Since we're dealing with official lineageos we assume selinux would be enforcing
You want to search for this string "permissive=1". On Linux just do cat console-ramoops-0 | grep "audit" (quotes are part of the command)
If you're on windows then you can download Linux and get the logs. Stop bothering me
If you see the string "permissive=1" in the log you have accidentally fetched a recovery log
Go back and boot again and wait for about a minute if selinux is permissive
The string should read
"permissive=0"
That means selinux is enforcing and this is indeed a ROM log
Send this log here
Hello,
Was this problem ever solved? I am experiencing the very same thing with every single ROM i have tried so far. TWRP is installed, I can install all ROMS but when I try to boot the phone, it just won't get passed the booting animation.
Thank you
My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)
update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.
Also, if you have root the TWRP app can flash recovery from in the OS.
Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
devam1995 said:
Dont panic just download a fast boot rom for version 9.0.11 and run it from fastboot using terminal. Then you will need to flash Magisk in order to have root access.
Click to expand...
Click to collapse
How do you do that using the terminal? I tried following this topic https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 but I got this error
https://imgur.com/wy1immW
TWRP still can't flash OOS
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
Flash a patched
Code:
boot.img
when I got the problem, I did that and it worked, booted me to system but if that doesn't work then you have to flash Magisk.
twistingthai said:
So I was able to boot the phone up again using MSMdownloadTool but the problem still persist. I was supposed to be at OOS 9.0.11 but upon checking I found out I was still on open beta 3. Tried to flash 9.0.11 via TWRP and the same thing happened. I was on slot B so when I flashed OOS and rebooted, it rebooted to slot A and brought me straight back to TWRP. It won't boot again until I switch back to slot B to boot and slot B was still on open beta 3. Any thoughts?
Click to expand...
Click to collapse
This phone has A/B partitions and is able to store a backup version of the OS so if a new installed version doesn't boot it will revert back to the old one.
When Flashing, you need to flash "BOTH" slots.
If you used the MSM tool to boot, you just booted and not flashed.
The MSM tool will flash your phone, restore the stock recovery and relic the bootloader. It will look like it came out of the box.
I don't know how to get you from wrapped around the axle except to tell you to run the MSM tool and let it wipe the phone and get you back to stock. You can then unlock the BL again and install TWRP, etc if you like.
twistingthai said:
I was on beta 3 and decided to flash a new version of OOS. I flashed 9.0.11 -> reflashed TWRP and magisk but when I rebooted, it went straight back to TWRP.
I had to switch to a different slot and the phone booted to OOS beta 3 again. Tried to flash 9.0.11 and reflashed beta 3 again but the same thing happened.
Then i swiped everything except for USB storage and Internal Storage in TWRP and now the phone is without OS.
I rebooted to TWRP and now TWRP lost the encryption and I can't flash anything anymore.
Does anybody know how to recover from this?
I'm using the official TWRP build.
Click to expand...
Click to collapse
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
parker.stephens said:
You are booting into TWRP because you did not format your data partition. When flashing OOS, you need to not only wipe data, but also under the Wipe menu, select format data. It should prompt you to type "yes".
Click to expand...
Click to collapse
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
twistingthai said:
This! Thanks to you I was able to flash OOS again. But do I need to format the data everytime I flash OOS because it will be a pain . This is the first time I had to format data when updating OOS. Thanks alot.
Click to expand...
Click to collapse
Glad to help. I was sick of having to put the device into Qualcomm mode just to get it to boot up, then I decided to try reformatting data and it worked.
I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...
There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?
Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!
downgrade twrp i has same prob twrp 3.3.1 gives issues
ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Seems the same with what i experienced. Have you tried installing a fastboot rom? I had my oneplus 6t bootlooped into fastboot mode even if i try to turn it off, it just boots back automatically to fastboot mode. Last resort was to flash a fastboot rom. That worked for me.
thalesian2020 said:
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Click to expand...
Click to collapse
What TWRP version are you trying to install?
jp0469 said:
What TWRP version are you trying to install?
Click to expand...
Click to collapse
I tried 3.3.1.1. and 3.2.3.0.
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Quickest way to start over:
To get back straight your gonna need to access a Windows PC, and run the MSM tool. Make sure you install both OnePlus and Qualcomm drivers. ( Don't wait for Windows, just pre install the drivers) here are some links. Not my work. Please be sure to thank the developers for creating and hosting these tools ?
MSM Tool:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
OnePlus Drivers:
https://androidfilehost.com/?fid=11410963190603879743
Qualcomm drivers:
https://androidfilehost.com/?fid=11410963190603879743
thalesian2020 said:
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Click to expand...
Click to collapse
Were you on Android 10 before (OOS)? That will do that. LOS 16 is Android 9 and should have no problems installing TWRP or booting to it.. For LOS 16 I'd go back to 9.0.17, then install LOS 6T.
I posted these LOS install instructions a long time ago for another user.
Remember the MSM Tool will relock your bootloader so if something goes wrong the MSM Tool is your only choice. That is why it is always the last thing I resort to.
Thread to get Fastboot stock Roms if you want to try that route first.
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
thalesian2020 said:
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
Click to expand...
Click to collapse
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
OhioYJ said:
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
Click to expand...
Click to collapse
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
thalesian2020 said:
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
Click to expand...
Click to collapse
Wiping, Dalvik / ART, System, and Vendor is generally a bad idea. You can do them in certain situations, this isn't one of those situations you should be wiping those though. Factory reset, means the slider on the main page of the wipe screen that says swipe to factory reset, format data is the button that says format data. Don't do anything extra. If you did, yeah I would go back to 9.0.17 using the fastboot rom again, that will put everything back on both slots.
like OhioYJ stated, don't use advanced wipe. re-run the msm tool. Then follow his instuctions. You shouldn't need to preform any manual data wiping. The process of flashing will do everything required. looks like you're almost there
Thanks guys. I will try it out and let you know.
Edit: So I finally managed to properly install LOS - OhioYJ, your instructions worked! I installed 9.0.17 and went from there without wiping any additional partitions.
One questions remains: in your instructions you mention that after installing LOS once, you can update LOS as normal and you mention doing it via the recovery with flashing TWRP or GAPPS later again. Is it possible to do the update via the normal update function of LOS as well? Or will that overwrite TWRP?
You guys are awesome. Thank you so much for your help!
I seem to be stuck on the fastboot screen as well. Being on a MAC, anytime i try to do something in fastboot it goes straight back to the fastboot screen. I Thought I was on Android 10.0 trying to install recovery for that lead to bootloop of fastboot, tried using the Pie recovery and same thing. I am open to suggestions.
Thanks.
OhioYJ said:
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Click to expand...
Click to collapse
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
callumbr1 said:
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
Click to expand...
Click to collapse
Yeah it starting to seem like it maybe isolated to Lineage. You cant install TWRP with LOS 17. Someone else mentioned in the Omni thread that it worked. This thread is about Lineage, but that should be clarified, or clearer.