Database Info

Can't install LineageOS

Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks

Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.

Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.

Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy

Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.

You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not

Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?

Wow idk what happened here. Mistakenly replied to this thread. Apologies.

Unable to install TWRP

Hello. I'm having trouble installing TWRP on my Pixel (sailfish) phone. Here's a detailed rundown to where I'm now.
I messed up by flashing the .zip file instead of booting from the .img. I restored the factory image following the instructions on the Factory Images page on Google Developers. Following that, I retried by closely following the instructions (booting into system, setting up PIN, enable debugging, rebooting into bootloader, etc.) Upon trying to install the .zip from the temporary TWRP boot, I get the errors
Code:
Failed to mount /system_data
Failed to mount /vendor
After this I'm unable to boot into recovery. Phone will get to Google screen, then shutdown and boot into system. I've tried a couple of things I've found online:
tried installing Verified Boot Signer with same errors
tried different versions of TWRP
tried factory resetting then wiping data from temporary TWRP boot
tried mounting partitions manually from menu; can only get vendor to mount
At this point I'm not sure what I might be missing. My goal is to install LineageOS + microG and rooting the device.
(Originally I tried using the Lineage Recovery for this following instructions unsuccessfully, so I'm trying TWRP instead. I'm including this in case it might have any relevance.)
Thanks in advance.

I dont have pixel,if pixel have 2 slots,u can try this way
Android = Fastboot mode.
PC to android = Fastboot boot twrp.img for temporary twrp.
Android = will display twrp,click install,pick twrp.img in android,click install ram disk,reboot system
Done
Try to reboot into recovery...it should be twrp recovery in permanently

Hello,I came to the same problom today,I tried to flash a LineageOS following this,and then install TWRP successfuly,It seemed that the latest google factory image was incompatitive with TWRP,that two partitions seem are new things that cannot be recognized by TWRP.Sorry for my poor English.
edit:It turns out no use,the TWRP app would crash and Recovery was the same.
edit again: I tried one older version of TWRP which is twrp-3.1.1-1,and It worked!

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine

Twrp boot loop

I patched twrp img with magisk and then ran fastboot flash boot "patched file" in fastboot mode. Now, whenever and however I start my system I get only the twrp menu. My device is Lenovo tab 4 8(tb-8504f)

Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.

re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work

jwoegerbauer said:
Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
hello thanks for replying. Could you provide me with the official rom. I've found one but not sure how reliable it is. I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore.

suraj123 said:
re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work
Click to expand...
Click to collapse
I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore. Does this include what you've refused me to do so? And can u pls provide me the official link?

TWRP works for latest OTA SPA2A.220405.003

Just so that everyone is aware because no one here seems to be aware of anything...
TWRP version twrp-3.6.1_11-0-redfin.img from here: https://dl.twrp.me/redfin/
Works just fine if you just temp boot from fastboot with the most recent OTA SPA2A.220405.003
And you DO NOT HAVE TO INSTALL A KERNEL FOR IT TO WORK, THIS BUILD ONLY
With this build, you can indeed backup and restore your system. I have used this build since it was live, and it works no problem.
I cannot confirm it works with any other build, nor can I confirm you can install it to ramdisk and get it to work.
But it works just fine with temp booting from fastboot. Backup, Restore, etc works just fine for me. I have gone back and forth from my build to the OTA no problem whatsoever, and have been able to restore all userdata from the most recent OTA.
BIG THANKS TO TWRP, AND bigbiff for his work

and, btw, you have to reboot anywhere from 1 to 3 times after a restore for it to completely boot.
You'll see the old boot logo first and it will freeze, then the new boot logo and it could freeze, then the third time it boots just fine. They even have this listed on TWRP's site I believe.
So, if you're having trouble after a restore, just reboot a few times but wait until it hangs before you do. It will eventually come up.

Also, it is possible to install this same recovery to your boot.img ramdisk. You cannot flash this image directly or else you will end up in a boot loop.
In order to install permanently to the ramdisk, you have to disable verity and verification just like for root, then temp boot the twrp.img, then while in recovery adb push twrp.img /
Then go to install, and choose the twrp.img and it will ramdisk install it. Then wipe all userdata--must be done, no way around it.
Reboot to recovery, and backup the boot.img only. Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img, then reboot to bootloader and flash the patched boot.
After all of that you will have both a rooted boot.img with permanent recovery in the ramdisk.
I do not know anything about safety net as I don't use any kind of banking apps at all so that will be your own responsibility to deal with.

That's so good to finally hear, looks like I'm going to have to do this. Thanks for the update, off topic but considering making a guide with as many links to projects, roms, kernels, etc that are being made or in process specifically for our phone and differentiating a11 and a12 support

stayboogy_Officially said:
Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img
Click to expand...
Click to collapse
This worked for me. I have Magisk and TWRP installed on stock Android 12.1 version 220305.
I was worried because I did not actively Disable Verity or Verification , or unencrypt anything.
But I am able to make full backups, and restore them, which is what i care about

I updated to Android build SP2A.220505.002 (via TWRP 3.6.2, magisk 24.3, and the May 2022 ota update file).
No problems yet..
has anyone updated to Android13 ?